-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
feat: add install-chromedriver command #366
Conversation
package.json
Outdated
@@ -33,7 +33,8 @@ | |||
"README.md", | |||
"CHANGELOG.md", | |||
"LICENSE", | |||
"npm-shrinkwrap.json" | |||
"npm-shrinkwrap.json", | |||
"scripts/*.mjs" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
simply include the whole scripts
dir
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure if we also need to add this folder to the list of linted sources
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, I might miss somewhere. npx eslint scripts/install-chromedriver.mjs
worked but npx eslint .
ignored the scripts
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps the global eslint config is only configured to verify .js files. We need to extend that and include mjs/cjs as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for now lets have the following pattern: (mjs|cjs|js|ts)
updated with the latest chromedriver |
package-lock.json
Outdated
@@ -1,15 +1,15 @@ | |||
{ | |||
"name": "appium-chromium-driver", | |||
"version": "1.3.54", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to keep package.lock? we have shrinkwrap though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe? I just respected existing one. Let me do the removal after this PR
README.md
Outdated
- macOS/Linux: `CHROMEDRIVER_VERSION=131.0.6778.3 appium driver run chromium install-chromedriver` | ||
- Windows: `$env:CHROMEDRIVER_VERSION='131.0.6778.3'; appium driver run chromium install-chromedriver; Remove-Item Env:\CHROMEDRIVER_VERSION` | ||
- `CHROMELABS_URL` | ||
- Let the command get the list of available chromedrivers from instead of the default `https://googlechromelabs.github.io`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from the given mirror instead of the default one
## [1.4.0](v1.3.57...v1.4.0) (2024-10-23) ### Features * add install-chromedriver command ([#366](#366)) ([4fb78e4](4fb78e4))
🎉 This PR is included in version 1.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Let's add the same automatic download (latest one) which is removed from appium-chromedriver.
This command will give the below log's ability.
#363