The files have exactly the same content, but there are a handful of differences in how npm handles them, most of which are noted on the docs pages for package-lock.json and npm-shrinkwrap.json:
package-lock.jsonis never published to npm, whereasnpm-shrinkwrapis by defaultpackage-lock.jsonfiles that are not in the top-level package are ignored, but shrinkwrap files belonging to dependencies are respectednpm-shrinkwrap.jsonis backwards-compatible with npm versions 2, 3, and 4, whereaspackage-lock.jsonis only recognized by npm 5+
You can convert an existing package-lock.json to an npm-shrinkwrap.json by running npm shrinkwrap.
Thus:
-
If you are not publishing your package to npm, the choice between these two files is of little consequence. You may wish to use
package-lock.jsonbecause it is the default and its name is clearer to npm beginners; alternatively, you may wish to usenpm-shrinkwrap.jsonfor backwards compatibility with npm 2-4 if it is difficult for you to ensure everyone on your development team is on npm 5+. (Note that npm 5 was released on 25th May 2017; backwards compatibility will become less and less important the further we get from that date, as most people will eventually upgrade.) -
If you are publishing your package to npm, you have a choice between:
- using a
package-lock.jsonto record exactly which versions of dependencies you installed, but allowing people installing your package to use any version of the dependencies that is compatible with the version ranges dictated by yourpackage.json, or - using an
npm-shrinkwrap.jsonto guarantee that everyone who installs your package gets exactly the same version of all dependencies
The official view described in the docs is that option 1 should be used for libraries (presumably in order to reduce the amount of package duplication caused when lots of a package’s dependencies all depend on slightly different versions of the same secondary dependency), but that option 2 might be reasonable for executables that are going to be installed globally.
- using a