Reference
Reference for semantic version ranges and operators.
Runs entirely in your browser
Nothing you paste is uploaded. Monaco and Prettier load on demand from this origin.
Search
| Range | Name | Matches |
|---|---|---|
| 1.2.3 | Exact | Only that exact version. |
| ^1.2.3 | Caret | >=1.2.3 <2.0.0 (compatible minor/patch). |
| ~1.2.3 | Tilde | >=1.2.3 <1.3.0 (patch only). |
| >=1.2.0 | Comparator | Greater than or equal. |
| 1.2.x | X-range | Any patch of 1.2. |
| 1.2.3 - 2.0.0 | Range | Inclusive hyphen range. |
| * | Any | Any version. |
| 1.2.3-beta.1 | Prerelease | Pre-release identifier. |
There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check. See how it stays private.
How to semantic versioning
- Read the rules. See when to bump major, minor, or patch.
- Check a range. Understand what ^1.2.0 or ~1.2.0 allows.
- Apply it. Version your package or set a dependency range.
SemVer is the contract that makes dependency management predictable: a version number tells consumers whether an update is safe. Knowing the range operators prevents both accidental breakage and needlessly pinned dependencies.
Generate a matching LICENSE and README badges for your package with the other dev generators.
Frequently asked questions
What does ^1.2.3 allow?
The caret allows updates that don't change the leftmost non-zero version — so ^1.2.3 permits 1.x.x but not 2.0.0, keeping compatible updates.
When should I bump the major version?
On any breaking change to your public API. Minor is for backward-compatible features; patch is for backward-compatible bug fixes.
Is anything fetched?
No. The list ships with the tool and works offline.