Compare & Sort Semantic Versions

No. 1.0.0+build.5 and 1.0.0+build.9 are equal in semver.

If two ranges share no version, no single install can satisfy both — the cause of peer dependency errors.

Only the package name when you load live versions from the npm or GitHub API. Ranges and versions you type are evaluated locally in your browser.

Only the package name when you load live versions from the npm or GitHub API. Ranges and versions you type are evaluated locally in your browser.

Paste versions to sort them properly (1.10 after 1.9), compare two releases or test if two ranges overlap.

Same algorithm as npm (node-semver) · runs in your browser

Compare two versions

1.10.0-beta.3 is newer — a preminor change.

Major

Minor

Patch

Pre-release

—

Build

—

Major

Minor

Patch

Pre-release

beta.3

Build

—

Semver compares numbers, not text: 1.10.0 is newer than 1.9.0, and 1.0.0-rc.1 comes before 1.0.0.

Sort versions

0.9.1
1.2.0
1.9.9
1.10.0-alpha
1.10.0
2.0.0-rc.1
2.0.0

Do two ranges overlap? (peer dependency conflicts)

overlapSome version satisfies both.

Loading Tool...

Help shape Compare & Sort Semantic Versions

The bug you just noticed will fade in 3 minutes. The feature idea will vanish after your next tab switch. Crazy peps don't suffer silently.

0/1000

Frequently Asked Questions

Semver compares each number as a number, not as text, so 10 is greater than 9.

Before their release: 2.0.0-alpha < 2.0.0-rc.1 < 2.0.0.

No. 1.0.0+build.5 and 1.0.0+build.9 are equal in semver.

If two ranges share no version, no single install can satisfy both — the cause of peer dependency errors.

Only the package name when you load live versions from the npm or GitHub API. Ranges and versions you type are evaluated locally in your browser.