-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cli: force chrome bin path #700
Comments
sinedied
added a commit
to sinedied/axe-core-npm
that referenced
this issue
Apr 3, 2023
sinedied
added a commit
to sinedied/axe-core-npm
that referenced
this issue
Jul 5, 2023
sinedied
added a commit
to sinedied/axe-core-npm
that referenced
this issue
Aug 9, 2023
straker
added a commit
that referenced
this issue
Aug 22, 2023
* feat(cli): add --chrome-path option (#700) * refactor: rename option description Co-authored-by: Steven Lambert <[email protected]> --------- Co-authored-by: Steven Lambert <[email protected]>
This was referenced Aug 24, 2023
This was referenced Sep 5, 2023
Closed via #704 |
Closed
Merged
Closed
Closed
Merged
This was referenced Jul 17, 2024
This was referenced Sep 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Product: cli
Expectation:
I'm embedding the CLI in another NPM package pre-configured to work out of the box for our needs. In that context, I would like to install a working Chrome / Chromedriver combo to make sure it works on the target machine, so I would like to be able to force chromedriver and chrome binary paths to be used.
Actual: There's currently an option to force chromedriver path, but not to force chrome binary path.
Motivation: Add an option (or environment variable) so we can force the chrome path to be used.
The text was updated successfully, but these errors were encountered: