Ship & Quality · LOCAL TOOL

SemVer Precedence Desk

Order full major.minor.patch versions using Semantic Versioning 2.0.0 precedence, including numeric and lexical prerelease identifiers. Group entries that differ only in build metadata.

Runs in this page
No API call

WORKSPACEINPUT → RESULT

Your input

LOCAL

Result

Run the tool to see a result.

Your result will appear here. Input is not saved.

Browser-side processingNothing is sent to a tool API.

WHY THIS TOOL EXISTS

A focused job, not a black box.

Numeric prerelease identifiers are compared numerically with arbitrary-size integers. The output keeps the original version text while explaining why build variants can have equal precedence.

How to use it

Paste complete versions without a v prefix or version range.
Run the ascending sort.
Inspect equal-precedence groups before choosing a release artifact.

TRY A WORKING EXAMPLE

Start with known input.

Load this sample into the workspace, run the tool, and compare the result shown below.

Show sample input

{
  "versions": "1.0.0\n1.0.0-beta.11\n1.0.0-beta.2\n1.0.0-alpha\n1.0.0+build.2"
}

Expected sample result from the local tool

5 version(s) sorted by SemVer precedence.

{
  "ascending": [
    "1.0.0-alpha",
    "1.0.0-beta.2",
    "1.0.0-beta.11",
    "1.0.0",
    "1.0.0+build.2"
  ],
  "equalPrecedence": [
    [
      "1.0.0",
      "1.0.0+build.2"
    ]
  ]
}

Build metadata does not affect precedence. Version ranges and v-prefixed shorthand are not accepted.

LIMITS AND INTERPRETATION

What the result cannot tell you.

At most 2000 versions. Strict SemVer syntax; no range resolution, shorthand, release-date inference, or package-registry lookup. Build metadata does not change precedence.

Inputs are processed in this page and are not written to local storage.

Reference for this model

Read the standard alongside the supported scope above.

Semantic Versioning 2.0.0 ↗