Skip to content

npm warning EBADENGINE Unsupported engine #794

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

Closed
tpacent opened this issue Jan 26, 2023 · 3 comments
Closed

npm warning EBADENGINE Unsupported engine #794

tpacent opened this issue Jan 26, 2023 · 3 comments
Labels

Comments

@tpacent
Copy link

tpacent commented Jan 26, 2023

Current behavior

When using Node 16 (LTS) or greater,
install/update command triggers a warning:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '<14.7.0' },
npm WARN EBADENGINE   current: { node: 'v16.15.0', npm: '9.2.0' }
npm WARN EBADENGINE }

node-abort-controller docs say its not needed when using Node 14.7.0+.

Expected behavior

No warning is thrown when installing this package using Node 16+.

Steps to reproduce the issue

npm i fork-ts-checker-webpack-plugin

Issue reproduction repository

none needed

Environment

  • fork-ts-checker-webpack-plugin: 7.3.0
  • typescript: 4.9.4
  • eslint: 8.32.0
  • webpack: 5.75.0
  • os: Ubuntu 22.04.1 LTS
@tpacent tpacent added the bug label Jan 26, 2023
@tpacent
Copy link
Author

tpacent commented Jan 26, 2023

nevermind, it was a breaking change in node-abort-controller:
southpolesteve/node-abort-controller#39

Use

"overrides": {
    "node-abort-controller": "3.0.1"
  }

to pin the package to the previous build.

@tpacent tpacent closed this as not planned Won't fix, can't repro, duplicate, stale Jan 26, 2023
@avandorp
Copy link

The problem with override is that you have to put it into every package.json of all your tools using directly or indirectly node-abort-controller. Even if you have one in between which declares an override. If node-abort-controller isn't fixed shortly it would be nice if
"node-abort-controller": "^3.0.1"
could be changed to
"node-abort-controller": "3.0.1"
in fork-ts-check-webpack-plugin, fixing it for all its users.

@tpacent
Copy link
Author

tpacent commented Jan 26, 2023

@avandorp correct, override is a temporary fix until either fork-ts-checker or abort-controller release an update.

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

No branches or pull requests

2 participants