DevtoolsLog: 'DevtoolsLog',

Trace: 'Trace',

Accessibility: 'Accessibility',

AnchorElements: 'AnchorElements',

CacheContents: 'CacheContents',

ConsoleMessages: 'ConsoleMessages',

CSSUsage: 'CSSUsage',

Doctype: 'Doctype',

DOMStats: 'DOMStats',

EmbeddedContent: 'EmbeddedContent',

FontSize: 'FontSize',

Inputs: 'Inputs',

FullPageScreenshot: 'FullPageScreenshot',

GlobalListeners: 'GlobalListeners',

IFrameElements: 'IFrameElements',

ImageElements: 'ImageElements',

InstallabilityErrors: 'InstallabilityErrors',

InspectorIssues: 'InspectorIssues',

JsUsage: 'JsUsage',

LinkElements: 'LinkElements',

MainDocumentContent: 'MainDocumentContent',

MetaElements: 'MetaElements',

NetworkUserAgent: 'NetworkUserAgent',

OptimizedImages: 'OptimizedImages',

PasswordInputsWithPreventedPaste: 'PasswordInputsWithPreventedPaste',

ResponseCompression: 'ResponseCompression',

RobotsTxt: 'RobotsTxt',

ServiceWorker: 'ServiceWorker',

ScriptElements: 'ScriptElements',

Scripts: 'Scripts',

SourceMaps: 'SourceMaps',

Stacks: 'Stacks',

TagsBlockingFirstPaint: 'TagsBlockingFirstPaint',

TapTargets: 'TapTargets',

TraceElements: 'TraceElements',

ViewportDimensions: 'ViewportDimensions',

WebAppManifest: 'WebAppManifest',

devtoolsLogs: 'devtoolsLogs',

traces: 'traces',

export default {

import lighthouse from 'lighthouse';

import config from './path/to/custom-config.js';

await lighthouse('https://example.com/', {port: 9222}, config);

The list of artifacts to collect on a single Lighthouse run. This property is required and on extension will be concatenated with the existing set of artifacts.

artifacts: [

{id: 'Accessibility', gatherer: 'accessibility'},

{id: 'AnchorElements', gatherer: 'anchor-elements'},

| id | `string` | Unique identifier for this artifact. This is how the artifact is referenced in audits. |

| gatherer | `string` | Gatherer used to produce this artifact. Does not need to be unique within the `artifacts` list. |

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/master/docs/user-flows.md).

- v9 configuration docs: https://github.com/GoogleChrome/lighthouse/blob/branch-9/docs/configuration.md

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/master/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/master/core/config/constants.js).

{

passes: [

{

passName: 'fastPass',

gatherers: ['fast-gatherer'],

},

{

passName: 'slowPass',

recordTrace: true,

useThrottling: true,

networkQuietThresholdMs: 5000,

gatherers: ['slow-gatherer'],

}

]

}

| 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/master/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. |

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.

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**

lighthouse --legacy-navigation --config-path=path/to/custom-config.js https://example.com

**Use config file via Node**

import {legacyNavigation} from 'lighthouse';

import config from './path/to/custom-config.js';

await legacyNavigation('https://example.com/', {port: 9222}, config);