Guide

THE TOOLBOX / PACKAGE MANAGEMENT & DEVOPS

SemVer Checker & Range Calculator —
Test npm ^, ~, Prereleases & Constraint Resolution Locally.

Evaluate Semantic Versioning ranges (^, ~, >=, x, ||) against candidate versions using the exact npm semver engine—instantly seeing normalized comparators, maxSatisfying, and release bumps.

Operators:

Comparator: >=1.2.3 <2.0.0-0

Matching
4 / 13
Max Satisfying
1.9.4
Min Satisfying
1.2.3

Version Resolution Matrix

0.2.3NO
0.2.9NO
0.3.0NO
1.2.2NO
1.2.3MATCH
1.2.9MATCH
1.5.0MATCH
1.9.4MAX MATCH
2.0.0-beta.1NO
2.0.0NO
2.1.5NO
2.2.0NO
3.0.0NO

SEMVER OPERATOR CHEAT SHEET

Common npm SemVer Range Expressions.

RangeExpanded ComparatorAllows
^1.2.3>=1.2.3 <2.0.0Minor & patch updates within 1.x
~1.2.3>=1.2.3 <1.3.0Patch updates within 1.2.x only
^0.2.3>=0.2.3 <0.3.0Patch updates only (0.x treats minor as breaking)
1.2.x || ^2.0.0(>=1.2.0 <1.3.0) OR (>=2.0.0 <3.0.0)Union of multiple disjoint version ranges

2. Exact npm node-semver Parity

Evaluated directly in your browser using the official semver package for 100% parity with package.json resolution.

Frequently Asked Questions

What is the difference between caret (^) and tilde (~) in SemVer?

Caret (^1.2.3) allows minor and patch updates that do not change the leftmost non-zero digit (>=1.2.3 <2.0.0). Tilde (~1.2.3) is stricter and only allows patch-level updates (>=1.2.3 <1.3.0).

How does caret (^) behave for 0.x.y pre-1.0 versions?

For 0.x versions, SemVer treats the minor version as breaking: ^0.2.3 resolves to >=0.2.3 <0.3.0, and ^0.0.3 resolves strictly to >=0.0.3 <0.0.4.

Why do prerelease versions like 2.0.0-beta.1 not match >=1.0.0 by default?

Under npm’s node-semver rules, prerelease tags are excluded from range matching unless a comparator in the same tuple explicitly includes a prerelease on that exact major.minor.patch, or includePrerelease is enabled.