Add quoting advice for PowerShell CLI options

[MikeMcC399]

• closes Cypress PowerShell: broken comma-separated-values CLI parsing since NodeJS 22.0.0 #6166

Situation

CLI options that include multiple values separated with commas, such as for --config, --env or --reporter-options may be misinterpreted when executing Cypress CLI in PowerShell on Windows.

The following documentation example cypress run --config generally fails to run in PowerShell 7.5.1 on Windows 11 24H2, Cypress 14.3.2 with package managers: npm, pnpm and Yarn:

cypress run --config pageLoadTimeout=100000,watchForFileChanges=false

The error is:

An invalid configuration value was set.

Expected pageLoadTimeout to be a number.

Instead the value was: "100000 watchForFileChanges=false"

An exception is npm@10.8.2 under Node.js v20.19.1 using npx cypress run where it works correctly.

Using PowerShell 7.5.1 on Ubuntu 24.04.2 LTS shows no issues with executing the above command in each of the package managers (npm, pnpm and Yarn).

Change

Add an info admonition to https://docs.cypress.io/app/references/command-line to advise enclosing the options in quotes:

When cypress run options or cypress open options are specified with multiple values separated by commas, such as for --config or --env options, and you are using PowerShell on Windows, you may need to surround the key/value pairs with quotes, for example: --env "host=api.dev.local,port=4222".

[netlify]

👷 Deploy request for cypress-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	d8d5eb0

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[MikeMcC399]