package-lock.json is automatically generated for any operations where npm modifies either package.json or the node_modules tree (default as of npm ^5.x.x).If you’re collaborating on a shared project with multiple developers, and you want to ensures that installations remain identical for all developers and environments, you need to use package-lock.json.Let us know on twitter or in the comments if there are any other tricks that we should include, or if you have any semver questions. This means that >1.4.0-c will include any tagged version that starts with c, d, e. One thing to note, the comparison for prerelease tags takes into account alphabetical order. For example, >1.4.0-beta.0 includes all the betas for version 1.4.0. You can also use comparators like > to include a range of prereleases for a particular version. To do this, you include the prerelease tag in the version number. But sometimes you want to include them anyway. This is because prerelease versions are meant to be unstable and are expected to have breaking changes. Include prerelease versionsīy default, prerelease versions are not included in a range. You can even chain these together to create very complex ranges, though you should only do that if you really really need to (which you probably don’t). You can set ~ as the default on your local machine with npm config set save-prefix='~'.

This would mean that you want either 1.3.15 or a higher version number that starts with 1.3 (it is in the same minor range). This tells npm that you want either 1.3.15 or a version that is greater than that but still starts with 1 (it is in the same major range). For example, npm install -save angular would add 'angular': '^1.3.15' to the dependencies in your package.json. The caret (aka hat) symbol, ^, is used by default when you npm install -save a package. Some semver ranges you might want to try… The basics: caret and tilde With it, you can test out even the most intricate of semver ranges to see if they mean what you think they mean. That’s why we’re introducing the npm semantic version calculator. It turns out that there is a range which allows that, 1.3.x || >1.4.0-beta.0, but when I asked around, very few people knew that… including folks at npm.

He was looking for a semver range for Angular that would include everything in the 1.3.x range and would also allow the beta version of 1.4.0. Introducing the npm semantic version calculatorĪ few weeks back, I saw a question from Kent Dodds about semver. Updates from the npm team are now published on the

Npm config set save prefix