Respect package.json update policy for packages
See original GitHub issueIn my package.json
I’m using pinned versions. It would be cool to keep it that away after doing updates.
I would even expect that it can be set per-package. So if one package uses ~
or ^
or exact version (installed with --save-exact
) it should not be altered in the resulting package.json
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
How to Upgrade Dependencies in Your package.json
After identifying the outdated packages, we fix the version specifications in package.json accordingly. Then we can run npm install or npm update to...
Read more >npm-update
This command will update all the packages listed to the latest version (specified by the tag config), respecting the semver constraints of both...
Read more >npm update is not updating the version in package.json file
The objective of the npm update command is to update your package-lock.json according to what you have specified in the package.json file.
Read more >package.json Quick Start Guide | phoenixNAP KB
Therefore, the value should respect the naming conventions of all three cases. For published packages, the name must be unique. Check the npm ......
Read more >Node JS: Package Management with NPM, Package.Json ...
Npm also supports downloading specific versions of packages. The ability to install a specific version of a certain package is useful 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 FreeTop 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
Top GitHub Comments
There is now a
--save-exact
feature, thanks to @pgilad https://github.com/dylang/npm-check/pull/91npm i -g npm-check
to get version 5 which has this feature.+1 … changes my exact version to
^
, which is unfortunate.