Software Version / Package Tools

Version Range Calculator

Expand an npm/SemVer range such as ^1.2.3 or 1.x into exact bounds, find the lowest matching version, test versions and check whether two ranges overlap.

Enter a version range in npm syntax to expand it into precise lower and upper bounds, then test versions against it or compare it with a second range.

Version range (npm / node-semver syntax)

Include prereleases (like --include-prerelease)

Versions to test (optional, one per line)

Second range to check overlap (optional)

Useful when two dependencies need the same package: if their ranges don't overlap, no single version can satisfy both.

More Software Version / Package Tools

View all 9

Package Name Validator SemVer Validator Dependency Version Comparator Version Comparator Python Requirements Version Helper Version Increment Generator Composer Version Constraint Helper npm Package Version Checker

Ranges starting with 0 behave differently - ^0.2.3 only allows patch updates - so check them here before relying on automatic updates.

What Is the Version Range Calculator?

It expands the shorthand used in package.json and many other tools - ^, ~, x/* wildcards, hyphen ranges, comparison operators and || - into exact comparators, using the same rules as npm's node-semver library.

When to Use It

Choosing how loose a dependency range should be.
Checking why a version was or wasn't installed.
Seeing whether two packages that need the same dependency can agree on one version.

How to Use It

Enter a range or click an example.
Optionally list versions to test and a second range to check overlap.
Tick "Include prereleases" to mimic --include-prerelease.

Examples

^1.2.3 → >=1.2.3 <2.0.0-0 (any 1.x from 1.2.3).
^0.2.3 → >=0.2.3 <0.3.0-0; ^0.0.3 → only 0.0.3.
~1.2 → >=1.2.0 <1.3.0-0.
1.2.3 - 2.3 → >=1.2.3 <2.4.0-0.

Understanding the Result

An upper bound like <2.0.0-0 means "below 2.0.0, and none of 2.0.0's prereleases either". By default a prerelease only matches if the range names a prerelease of the same MAJOR.MINOR.PATCH - so ^1.2.3 does not match 1.5.0-beta. The lowest matching version is what a range with no upper limit starts from.

Limitations

This follows npm/node-semver syntax. Composer's ~ means something different - use the Composer Version Constraint Helper - and Python uses PEP 440 specifiers. To check a spec against a package's published versions, use the npm Package Version Checker.