NPM version requires ^3.0.0
See original GitHub issueDescription
This library requires the carat (^
) of npm for 3.0.0
-> ^3.0.0
this causes issues for any packages consuming this library that require newer versions of npm because the ^
indicates that the left-most (major) version cannot be increased.
is there any reason we can’t remove this restriction? or do newer versions of npm break this library?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:15
Top Results From Across the Web
3.0.0 - npm
a package manager for JavaScript. Latest version: 9.2.0, last published: 7 days ago. Start using npm in your project by running `npm i...
Read more >How to install a previous exact version of a NPM package
and I get an error that express requires node version >= 0.5.0. How do npm fetch a version that ... For example: npm...
Read more >NPM installs different version from package.json
I ran into similar issue where instead of required tildify 2.0.0 it was always installing 3.0.0 version.
Read more >npm Application Analysis - Sonatype Help
For npm, scanning the package-lock.json is required. ... Scan the project with the CI or CLI scanners after the npm 'install' command has...
Read more >The Complete Guide to package-lock.json - Medium
^2.3.0 — [Caret Symbol] This tells npm to upgrade to minor and patch versions, but not major versions. So, basically 2.3.4, 2.3.9, 2.4.5,...
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
you can downgrade your node version to a version that uses npm 3.X.X and after installing return to your original node version.
this error shows up every time i install a package