The first list includes all packages that can’t be installed due to the defined version range in your package.json file. Notice that the list of outdated packages is different from NPM’s overview. Update the dependencies in your package file anyway, run ncu -a. Without modifying your package file by using npm update. The following dependencies are satisfied by their declared version range,īut the installed versions are behind. Run it in your project’s folder to check the project’s dependencies for updates: $ ncu Install the command line tool globally on your machine with this command: npm install -g npm-check-updatesĪs soon as the package installation finished, you’ll have the ncu command available on your computer.
The npm-check-updates package is a convenient helper providing useful features for dependency upgrades. But wait, there’s help! NPM-Check-Updates You need to manually go through your package.json file and bump all versions. The downside: there’s no command in NPM’s CLI to update all packages to their latest version. Review the installed version of a module, the wanted version satisfying the package’s version range and the latest version. Run npm outdated in a project directory to show a list of outdated packages. The NPM CLI shows outdated packages in your project. Over time, your project’s dependencies go out of date and you need to invest time into updating the third-party packages. You’ll regularly notice releases that contain new features or bug fixes. The development lifecycle of NPM packages is fast.
0 kommentar(er)
