Loading Depth Study
Preparing your workspace
Semantic versioning commonly uses major, minor, and patch numbers to communicate the nature of changes between releases.
A version such as 2.4.1 commonly follows the major.minor.patch pattern. Major releases may contain breaking changes, minor releases generally add compatible functionality, and patch releases usually contain compatible fixes. Package managers also support version ranges that control which versions can be installed. Understanding these ranges helps prevent unexpected dependency upgrades.
A project may intentionally allow compatible minor and patch updates while avoiding a new major version until the application has been tested against it.
"dependencies": {
"example-package": "^2.4.1",
"another-package": "~1.8.3"
}The project declares version ranges that control which package versions are acceptable during installation.