Npm-check-updates updates only package.json, you need to run npm install after it. You'll have to answer to every question, even if you want to update only the first few. It's not possible to end progress with saving progress in the middle of dependency questions. Npm-check-updates has an interactive mode, where it asks whether it should update each dependency: Unlike npm update it updates everything to the latest version ignoring the semver range specified in the package.json. It shows version differences more clear than npm outdated. Npm-check-updates provides a much better experience than built-in tools. Npm update both updates package.json and installs new versions (no need to run npm install). With npm update the only option is to pin the version in package.json, and then unpin it when the dependency is fixed.Īfter npm update npm outdated shows remaining versions outside the specified semver range. Sometimes minor version has bugs, and we don't want to update them just yet. It is not possible to select only a few dependencies, so it installs everything. Npm update updates all dependencies to the highest version, matching the specified semver range (“wanted” column in npm outdated). And it shows highest dependency version, which in semver range specified in package.json. npm outdated shows dependencies, which has newer version. Tools npm outdated/ npm update īuilt-in npm outdated and npm update provide very basic experience.
1 Comment
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |