

MAJOR version (1.x.x), which can contain breaking changes, more significant updates.The semantic versioning means that we have a version number (1.2.3) with three digits: And this is the point where versioning is critical because it is easy to break things. There is a tremendous dependency in any project that we don’t know about. If you check the size of the node_modules folder in any of your projects, you will see the tens of thousands of files and the vast physical size. Managing packages is a big deal in modern development. To understand the package updating mechanism, first, we have to understand the versioning and the nature of npm.

Updating npm dependencies isn’t a big task, but sometimes it can be more complicated depending on our needs.
