← All tools

SemVer Comparator & Sorter: Strict 2.0.0 Precedence

Compare and sort strict semantic versions, explain prerelease precedence and ignore build metadata without rounding large numeric identifiers.

semver-comparatorLOCAL WORKSPACE

Enabling local controls…

1. Strict SemVer versions

Data stays in page memory. Batch: 1 MiB, 1000 versions; each version: 4096 characters. Versions require all three fields and reject v prefixes and leading zeroes.

Supports ^, ~, comparators, space intersections and || unions. Up to 8 groups, 8 clauses per group and 256 characters. Prereleases require an explicit prerelease clause with the same core version.

Prereleases rank below the same core release; numeric identifiers rank below nonnumeric ones. Build metadata never affects precedence. Ties preserve input order and duplicates; equal precedence does not mean identical text or guaranteed compatibility.

Original specification: Semantic Versioning 2.0.0

2. Precedence result

Load a sample or enter versions, then run.

How to use this tool

Compare two versions or sort one version per line. Review parsed identifiers and precedence; equal-precedence versions retain their input order.

When not to use it

Only SemVer 2.0.0, not npm ranges, loose v prefixes or package resolution. Build metadata does not determine precedence or prove binary equality or compatibility.