docs: remove legacy navigation (#15340)

Author: adamraine

docs/configuration.md

@@ -1,8 +1,3 @@
-<!---
-TODO(rm-legacy): Remove this when legacy path is gone.
--->
-> **WARNING**: This config format is for configs in version 10.0 and beyond. Please read the [legacy config](#legacy-configs) section if you are using the old config format.
-
 # Lighthouse Configuration
 
 The Lighthouse config object is the primary method of customizing Lighthouse to suit your use case. Using a custom config, you can limit the audits to run, add additional loads of the page under special conditions, add your own custom checks, tweak the scoring, and more.
@@ -45,7 +40,7 @@ await lighthouse('https://example.com/', {port: 9222}, config);
 | - | - | - |
 | extends | <code>string&#124;undefined</code> |
 | settings | <code>Object&#124;undefined</code> |
-| passes | <code>Object[]</code> |
+| artifacts | <code>Object[]</code> |
 | audits | <code>string[]</code> |
 | categories | <code>Object&#124;undefined</code> |
 | groups | <code>Object&#124;undefined</code> |
@@ -178,7 +173,7 @@ The groups property controls how to visually group audits within a category. For
 
 ## Config Extension
 
-The stock Lighthouse configurations can be extended if you only need to make small tweaks, such as adding an audit or skipping an audit, but wish to still run most of what Lighthouse offers. When adding the `extends: 'lighthouse:default'` property to your config, the default passes, audits, groups, and categories will be automatically included, allowing you modify settings or add additional audits to a pass.
+The stock Lighthouse configurations can be extended if you only need to make small tweaks, such as adding an audit or skipping an audit, but wish to still run most of what Lighthouse offers. When adding the `extends: 'lighthouse:default'` property to your config, the artifacts, audits, groups, and categories will be automatically included, allowing you modify settings or add additional audits and artifacts.
 
 Please note that the `extends` property only supports extension of `lighthouse:default`. Other internal configs found in the [core/config](https://github.com/GoogleChrome/lighthouse/tree/main/core/config) directory can be used by importing the config object from file reference, or by using the [`--preset`](https://github.com/GoogleChrome/lighthouse#cli-options) CLI flag.
 
@@ -196,69 +191,3 @@ The best examples are the ones Lighthouse uses itself! There are several referen
 * [core/config/perf-config.js](https://github.com/GoogleChrome/lighthouse/blob/main/core/config/perf-config.js)
 * [docs/recipes/custom-audit/custom-config.js](https://github.com/GoogleChrome/lighthouse/blob/main/docs/recipes/custom-audit/custom-config.js)
 * [pwmetrics](https://github.com/paulirish/pwmetrics/blob/v4.1.1/lib/perf-config.ts)
-
-## Legacy Configs
-
-Older versions of Lighthouse (pre-10.0) use a slightly different config format. The biggest difference is that the new configs do not include `passes`. If you want to load a page multiple times, we recommend creating a [user flow](https://github.com/GoogleChrome/lighthouse/blob/main/docs/user-flows.md).
-
-- v9 configuration docs: https://github.com/GoogleChrome/lighthouse/blob/branch-9/docs/configuration.md
-
-### `passes: Object[]`
-
-The passes property controls how to load the requested URL and what information to gather about the page while loading. Each entry in the passes array represents one load of the page (e.g. 4 entries in `passes` will load the page 4 times), so be judicious about adding multiple entries here to avoid extending run times.
-
-Each `passes` entry defines basic settings such as how long to wait for the page to load and whether to record a trace file. Additionally a list of **gatherers** to use is defined per pass. Gatherers can read information from the page to generate artifacts which are later used by audits to provide you with a Lighthouse report. For more information on implementing a custom gatherer and the role they play in building a Lighthouse report, refer to the [recipes](https://github.com/GoogleChrome/lighthouse/blob/main/docs/recipes/custom-audit). Also note that `artifacts.devtoolsLogs` will be automatically populated for every pass. Gatherers also have access to this data within the `afterPass` as `traceData.devtoolsLog` (However, most will find the higher-level `traceData.networkRecords` more useful).
-
-For list of default pass values, see [our config constants](https://github.com/GoogleChrome/lighthouse/blob/main/core/config/constants.js).
-
-#### Example
-```js
-{
-  passes: [
-    {
-      passName: 'fastPass',
-      gatherers: ['fast-gatherer'],
-    },
-    {
-      passName: 'slowPass',
-      recordTrace: true,
-      useThrottling: true,
-      networkQuietThresholdMs: 5000,
-      gatherers: ['slow-gatherer'],
-    }
-  ]
-}
-```
-
-#### Options
-| Name | Type | Description |
-| -- | -- | -- |
-| passName | `string` | A unique identifier for the pass used in audits and during config extension. |
-| recordTrace | `boolean` | Records a [trace](https://github.com/GoogleChrome/lighthouse/blob/main/docs/architecture.md#understanding-a-trace) of the pass when enabled. Available to gatherers during `afterPass` as `traceData.trace` and to audits in `artifacts.traces`. |
-| useThrottling | `boolean` | Enables throttling of the pass when enabled. |
-| pauseAfterLoadMs | `number` | The number of milliseconds to wait after the load event before the pass can continue. Used to ensure the page has had time for post-load JavaScript to execute before ending a trace. (Default: 0) |
-| networkQuietThresholdMs | `number` | The number of milliseconds since the last network request to wait before the page should be considered to have reached 'network quiet'. Used to ensure the page has had time for the full waterfall of network requests to complete before ending a trace. (Default: 5000) |
-| pauseAfterNetworkQuietMs | `number` | The number of milliseconds to wait after 'network quiet' before the pass can continue. Used to ensure the page has had time for post-network-quiet JavaScript to execute before ending a trace. (Default: 0) |
-| blockedUrlPatterns | `string[]` | URLs of requests to block while loading the page. Basic wildcard support using `*`.  |
-| gatherers | `string[]` | The list of gatherers to run on this pass. This property is required and on extension will be concatenated with the existing set of gatherers. |
-
-### Migrating to 10.0 format
-
-1. Combine the gatherer lists in [`config.passes`](#passes-object) into [`config.artifacts`](#artifacts-object), giving each artifact a unique ID.
-1. Remove [`config.passes`](#passes-object) property. Pass properties such as `pauseAfterLoadMs` are defined on `config.settings` in 10.0 configs.
-
-### Using legacy configs in 10.0
-
-The old config format can still be used in 10.0 but it's behind a separate path in the CLI and Node API.
-
-**Use config file via CLI**
-```sh
-lighthouse --legacy-navigation --config-path=path/to/custom-config.js https://example.com
-```
-
-**Use config file via Node**
-```js
-import {legacyNavigation} from 'lighthouse';
-import config from './path/to/custom-config.js';
-await legacyNavigation('https://example.com/', {port: 9222}, config);
-```

docs/readme.md

@@ -113,8 +113,6 @@ Lighthouse can run against a real mobile device. You can follow the [Remote Debu
 
 You'll likely want to use the CLI flags `--screenEmulation.disabled --throttling.cpuSlowdownMultiplier=1 --throttling-method=provided` to disable any additional emulation.
 
-> **Warning:** If you are running Lighthouse 10.x with any chrome version older than M112 (<=M111) you will need to add the `--legacy-navigation` to the `lighthouse` command. See https://github.com/GoogleChrome/lighthouse/issues/14746 for more info.
-
 ```sh
 $ adb kill-server
 

docs/recipes/custom-audit/readme.md

@@ -21,7 +21,7 @@ find the gatherer and audit files, when to run them, and how to incorporate thei
 output into the Lighthouse report. This example extends [Lighthouse's
 default configuration](https://github.com/GoogleChrome/lighthouse/blob/main/core/config/default-config.js).
 
-**Note**: when extending the default configuration file, passes with the same name are merged together, all other arrays will be concatenated, and primitive values will override the defaults.
+**Note**: when extending the default configuration file, all arrays will be concatenated and primitive values will override the defaults.
 
 ## Run the configuration