Member-only story
How to Upgrade Dependencies in Your package.json
Check outdated packages and update them properly

Npm (Node Package Manager) is a package manager for the JavaScript programming language. It is the default package manager for the JavaScript runtime environment Node.js.
A project keeps its package dependency list in package.json
. For each installed package, a version is assigned. Typically, a version is made up of three parts: major.minor.patch.
- Major is for the incompatible API changes.
- Minor is for the backward-compatible functionality.
- Patch is for the backward-compatible bug fixes.
By default, npm installs the latest version, and prepends a caret, such as “^15.2.0”. The caret dependency suggests that minimally, 15.2.0 should be installed.
When a higher minor version exists, it would be used. If the highest minor version at the time being is 15.6.2, this particular version, 15.6.2, will be upgraded to.
If you want to be a little conservative, the tilde dependency, “~15.2.0”, would suggest only a higher patch version would be used. Of course, the plain “15.2.0” would guarantee that only the exact version is used. The details of semantic versioning are defined by SemVer.