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.
Enabling local controls…
1. Strict SemVer versions
Data stays in page memory. Batch: 1 MiB, 1000 versions; each version: 4096 characters. Requires all three fields; no npm ranges, v prefix or leading zeroes.
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.
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.