basketfalo.blogg.se - Npm updates

There used to be an annoyance that npm update did not update the package.json file but this is no longer the case from 5.0.0. On the other hand, npm update will do all of that, and not give you the chance to check what is being updated beforehand. Once you've run that command, you'll then need to run a separate npm install to grab those changes. Npm-check-updates will only modify your package.json file. Ncu -target - choose which type of version to list/update. For that, you will need to run npm install. It will change the versions of all the dependencies in package.json to the latest (even if it's a breaking version!), but will not modify the package-lock.json file. Ncu -update - apply changes to the package.json file only. Running ncu without any flags will print a list of all the outdated packages and the version to which it would update, but will not apply any changes. It prints a table that includes the package, the current version, the wanted version - according to the semver rules in the package.json - the latest version and the location of the package. Npm outdated - shows all the packages that have newer versions available, this includes breaking changes.

and above) You can see the changes npm update will perform with the flag -dry-run, without actually updating.

However, this flag will completely ignore package-lock.json and hence automatic pruning of extraneous modules will also be disabled.

and above) You can choose to update only the package.json file with npm update -package-lock false.

It will never update to a breaking version.

Npm update - updates the dependencies both in package.json and package-lock.json in accordance to the semantic version rules defined in package.json. A bit late to the party but I felt like the previously accepted answer is outdated and slightly lacking.