This will update the local node_modules repository with the versions present in package.json. This will update the package.json file as per latest versions available in npm repositories on web.

In summary, if you want to update your node modules to latest versions respecting the semver then it is a two step process. Now if you issue the npm install command, the new versions from the updated package.json file are installed to your local repository. The ncu –u command will modify the package.json file with the latest version available in npm repositories. Similarly current version of ‘body-parser’ is ~1.8.1 but the latest version available in npm repositories respecting the ~ is 1.17.1. The above output shows that for ‘express’ the current version installed is ~4.9.0 but the latest version available respecting ~ is 4.15.2. The ncu command is a short form of npm-check-updates and produces the output shown above without changing anything. Once the utility is installed globally, you can invoke it as follows: First install it by running the following command:

The npm-check-updates utility comes to rescue. So what is the best way to avoid this discrepancy? This leads to confusion since there is mismatch between the installed versions in node_modules repository and the versions mentioned in package.json file. However, the most annoying aspect of running the update command is that although the modules are updated to the latest versions, the versions mentioned in the package.json file are not changed. It installs the latest versions of modules from the npm repositories while respecting the caret and tilde dependencies specified in the package.json file. The command npm update updates all modules present in package.json to their latest versions. The command does not update any module to latest version.

The command npm install reads the module names and their corresponding versions from package.json file and installs them in node_modules folder.

There are situations when some Node.js modules in the application become obsolete and need to be updated to the latest versions. Information Protection and Compliance (17).SharePoint On-Prem to SharePoint Online Migration (6).Microsoft 365 Tenant-to-Tenant Migration (4).Google Workspace to Microsoft 365 Migration (8).Documentum to Microsoft 365 Migration (2).Cloud Infrastructure and Management (56).

Windows node update