How do you keep package-lock.json updated?
See original GitHub issueThis project uses npm5’s package-lock.json
, I realised that a lot of folks use yarn or an older version of npm.
What this means is that you might not get the same dependencies on your machines.
Moreover, dependencies you add on npm4 will not get added to package-lock
, this might lead to problems in CI which uses npm5 and will only install packages from package-lock (If I understand correctly, I might be wrong)
How do we get around this problem?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
package-locks - npm Docs
Using a locked package is no different than using any package without a package lock: any commands that update node_modules and/or package.json 's...
Read more >How to update package-lock.json without doing npm install?
The --package-lock-only argument will only update the package-lock.json , instead of checking node_modules and downloading dependencies. yarn.
Read more >The Complete Guide to package-lock.json - Medium
The package-lock. json file ensures that the same node_modules tree is generated every time npm install is run. A newer command npm ci...
Read more >How to Upgrade Dependencies in Your package.json
A project keeps its package dependency list in package.json . ... if we run npm update , Prettier's version is upgraded to “1.8.2”...
Read more >package-lock.json not updated when saving package.json file
I do not think there is a way to only have it update the package-lock file without also performing another save on 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 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
Hi @tohjustin!
I’ll do that today ☺️
Can add npm engines to package.json which I think throws a warning if under the version. https://docs.npmjs.com/files/package.json#engines