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.
v1.16.3 introduced "node": ">=10" depencency
See original GitHub issueIn v1.16.3 packages were bumped, in particular semver from 6.3.0 to 7.1.3. In this new version of semver new dependency was introduced:
https://github.com/npm/node-semver/blob/master/package.json#L36
I’m not sure if this could be considered as breaking change but productions servers with lower node version harmed.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
node/CHANGELOG_V16.md at main · nodejs/node - GitHub
The node:test module, which was initially introduced in Node.js v18.0.0, is now available with all the changes done to it up to Node.js...
Read more >Node v12.16.3 (LTS)
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Read more >Upgrading Node.js to latest version - Stack Overflow
I have installed these versions of node and I have Windows 10 installed. I have installed express and jade globally but in my...
Read more >Node.js - CloudBees Documentation
You can use npm to install your dependencies. We set the $PATH to include the node_modules/.bin folder so all executables installed through npm...
Read more >How To Install and Use the Yarn Package Manager for Node.js
yarn install. This will download and install the modules you need to get started. Adding a New Dependency to a Project. Use the ......
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
Yep I overlooked this when using the sledgehammer of
yarn upgrade --latest. Apologies to anyone this affects. I plan to releasev1.16.4with semver pinned and then deprecatev1.16.3. Then maybe bump semver and drop node 8 support inv2.0.0.This is now done.