Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to use v12 with node v15+ ("engines.node" field misuse)
See original GitHub issueDescription
The engine "node" is incompatible with this module. Expected version "^12.14.1 || ^14.0.0". Got "15.14.0"
Minimal Reproduction
See the issue title.
Your Environment
node v15.14.0 (npm v7.7.6).
Angular Version:
v12 stack.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:15
- Comments:29 (9 by maintainers)
Top Results From Across the Web
The engine "node" is incompatible with this module
In my case, I am using yarn workspaces and some of the modules in the package.json files in the workspaces might require foo...
Read more >How To Run Multiple Versions of Node.js with ... - DigitalOcean
At this point, you have installed several versions of Node.js. You can use nvm to uninstall any unwanted version of Node.js you may...
Read more >Why is my Node.js build failing because of no ... - Heroku Help
Heroku recommends specifying the version of Node.js that you are using locally in the engines field. To find your version locally: $ node...
Read more >Deprecated APIs | Node.js v19.3.0 Documentation
Node.js APIs might be deprecated for any of the following reasons: Use of the API is unsafe. An improved alternative API is available....
Read more >Dependency Scanning Fails: "engine 'node' is incompatible ...
Dependency Scanning job fails presumably because it's installing dependencies with a newer version of Node engine that is not compatible with ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Wouldnt it be better to have a recommendation instead of forbidding to use newer versions? How it is right now it will fail hard: Local development is no more possible without use of
nvmand pipelines are failing.Update: We have decided to update the field to be less restrictive (see #42205).
We will work to surface the Node supported version information in the
ng versionoutput to express when an unsupported version of node is being used.