Recommend using a configuration JSON file.

https://github.com/sitespeedio/sitespeed.io/issues/4458
This commit is contained in:
Peter Hedenskog 2025-03-04 07:09:58 +01:00
parent 28093a4268
commit 39ff8259dc
2 changed files with 3 additions and 3 deletions

View File

@ -219,7 +219,7 @@ docker run --rm -v "$(pwd):/sitespeed.io" sitespeedio/sitespeed.io:{% include ve
The CLI will always override the JSON config.
You can also extend another JSON config file. The path needs to be absolute.
You can also extend another JSON config file. The path needs to be absolute. We recommend that you use a configuration file because that makes things easier.
~~~json
{
@ -239,7 +239,7 @@ You can also extend another JSON config file. The path needs to be absolute.
}
~~~
If you have a parameter that you want to repeat, for example setting multiple request headers, the field needs to be an JSON array.
If you have a parameter that you want to repeat, for example setting multiple request headers, the field needs to be an JSON array.
~~~json
{

View File

@ -521,7 +521,7 @@ export async function parseCommandLine() {
.option('browsertime.scriptInput.visualElements', {
alias: ['scriptInput.visualElements'],
describe:
'Include specific elements in visual elements. Give the element a name and select it with document.body.querySelector. Use like this: --scriptInput.visualElements name:domSelector . Add multiple instances to measure multiple elements. Visual Metrics will use these elements and calculate when they are visible and fully rendered.',
'Include specific elements in visual elements. Give the element a name and select it with document.body.querySelector. Use like this: --scriptInput.visualElements name:domSelector . If you want to measure multiple elements, use a configuration file with an array for the input. Visual Metrics will use these elements and calculate when they are visible and fully rendered.',
group: 'Browser'
})
.option('browsertime.scriptInput.longTask', {