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

[BrianFreedman]

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: selenium-webdriver@4.28.0
npm error notsup Not compatible with your version of node/npm: selenium-webdriver@4.28.0
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 selenium-webdriver@4.28.0

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

[github-actions]

@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]

I believe this was fixed by 889b309 and released Javascript selenium-webdriver@4.28.1

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.