Why is the node version limited to < 10?
See original GitHub issueThe docs say it “can be used either in Node >= 4 or in the browser”, but the package.json specifies node < 10
.
"engines": {
"node": ">=4 <10",
Just wondering if there’s anything in the current version that breaks this library? or if the package.json is just being overly restrictive?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
The Difference Between Node.js 10 LTS and Node.js 12 LTS
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Read more >Node Engines: Helping Developers Everywhere Avoid ...
Similarly, our React application needs Node version 10 or higher, to take advantage of all the ES6 and beyond node dependencies that it...
Read more >How to change Node Version in Provision Step in Amplify ...
AWS Amplify use nvm to handle node version. Try this: version: 0.1 backend: phases: ... In my case, I wanted the latest node...
Read more >Mastering Node.js version management and npm registry ...
Node version manager ... When developing Node.js applications, you may need to install multiple versions of Node.js in order to handle your day-to ......
Read more >How To Run Multiple Versions of Node.js with ... - DigitalOcean
You have the latest and greatest version of Node.js installed, and the project you're about to work on requires an older version. In...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
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
Sorry for the delay on this - PR up.
Fixed and released in 3.0.2