Semver Calculator

Semantic versioning (semver) is a version numbering convention using the MAJOR.MINOR.PATCH format. Increment MAJOR for breaking changes, MINOR for new backwards-compatible features, and PATCH for backwards-compatible bug fixes. For example, going from 1.2.3 to 2.0.0 signals a breaking change.

The caret (^) means 'compatible with' — it allows changes that do not modify the left-most non-zero version component. ^1.2.3 allows >=1.2.3 <2.0.0, so any 1.x.x version works. ^0.2.3 allows >=0.2.3 <0.3.0 because 0.x is the left-most non-zero digit.

The tilde (~) means 'approximately equivalent' — it allows patch-level changes if a minor version is specified. ~1.2.3 allows >=1.2.3 <1.3.0 (same minor, any patch). ~1.2 allows >=1.2.0 <1.3.0. This is more restrictive than ^ because it locks the minor version.

Bump MAJOR when you make incompatible API changes (removing a function, changing method signatures). Bump MINOR when you add backwards-compatible functionality (new methods, new optional parameters). Bump PATCH for backwards-compatible bug fixes only. Pre-release versions (1.0.0-alpha.1) and build metadata (1.0.0+build.1) are also part of the semver spec.

Use the Range Check tab. Enter the installed version (e.g. 1.5.3) and the constraint from package.json (e.g. ^1.0.0 or ~1.2.0 or >=1.0.0 <2.0.0). The calculator shows whether the version satisfies the range and explains why or why not.