Skip to content
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

[🐛 Bug]: required engines in package.json in webdriver 4.28.0 drops support for LTS versions of node #15120

Closed
BrianFreedman opened this issue Jan 20, 2025 · 2 comments

Comments

@BrianFreedman
Copy link

BrianFreedman commented Jan 20, 2025

What happened?

npm install fails when running on a LTS version of node that is not >= 22.13.0

as per https://github.com/SeleniumHQ/selenium/blob/1f68c82/javascript/node/selenium-webdriver/package.json#L23

here's the change where it went in:
https://github.com/SeleniumHQ/selenium/pull/15058/files

How can we reproduce the issue?

using any LTS of node 20:
with `engine-strict=true` set in your .npmrc file
run `npm install`

Relevant log output

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: [email protected]
npm error notsup Not compatible with your version of node/npm: [email protected]
npm error notsup Required: {"node":">= 22.13.0"}
npm error notsup Actual:   {"npm":"10.7.0","node":"v20.14.0"}

Operating System

Windows 11

Selenium version

Javascript [email protected]

What are the browser(s) and version(s) where you see this issue?

n/a

What are the browser driver(s) and version(s) where you see this issue?

n/a

Are you using Selenium Grid?

n/a

Copy link

@BrianFreedman, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

@VietND96
Copy link
Member

I believe this was fixed by 889b309 and released Javascript [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants