#moonsver

                      ┌──────────────┐
  "1.2.3-alpha+build" │  Version     │  parse / to_string
  ">=1.2.3, <2.0.0"   │  Range       │  precedence_cmp / satisfies
  "^1.2.3"  "~1.2"    │  Syntax      │  npm / cargo / ruby / strict
                      └──────────────┘

• SemVer 2.0.0 only. PEP 440 is not SemVer and is not implemented; 1.0.0.post1 and ~=1.4 are refused rather than guessed at.
• Arbitrary precision. The three numbers are BigInts, so 18446744073709551616.0.0 parses, prints and compares exactly. node-semver stops at the JavaScript safe integer, Rust's semver crate at u64.
• Aligned with the mature implementations. Precedence follows §11 of the spec to the letter; range expansion matches node-semver's replaceXRange / replaceCarets / replaceTildes and Cargo's caret rules.
• No third-party dependencies, just moonbitlang/core.

#Using it

import {
  "moonbitstack/moonsver",
}

// moon.work
members = [
  "vendor/moonsver",
]

// moon.mod
import {
  "moonbitstack/moonsver@0.1.0",
}

#Quick start

///|
fn demo() -> Unit raise @moonsver.Refused {
  // Parsing and printing
  let v = @moonsver.Version::parse("1.2.3-alpha.1+build.5")
  println(v.to_string())      // 1.2.3-alpha.1+build.5
  println(v.core_string())    // 1.2.3
  println(v.is_prerelease())  // true

  // Precedence (§11; build metadata stays out of it)
  let a = @moonsver.Version::parse("1.0.0-alpha")
  let b = @moonsver.Version::parse("1.0.0")
  println(a.precedence_cmp(b))  // -1

  // Ranges
  let r = @moonsver.Range::parse("^1.2.3")
  println(r.to_string())        // >=1.2.3, <2.0.0
  println(r.satisfies(@moonsver.Version::parse("1.9.0")))  // true
  println(r.satisfies(@moonsver.Version::parse("2.0.0")))  // false

  // Bumps
  println(@moonsver.Version::parse("1.2.3").inc(@moonsver.Major).to_string())  // 2.0.0
}

#API

#Version

#Release

#Range

#satisfies(version, range, syntax?)

#Errors

#Grammar settings (Syntax)

#The same string, three readings

#How it behaves

#Precedence (§11)

1. Compare major, minor, patch in turn (arbitrary precision);
2. a version with a prerelease ranks below the same numbers without one;
3. prerelease identifiers compare one by one: numeric by value, numeric below alphanumeric, alphanumeric in ASCII order;
4. a prefix ranks below the longer list;
5. build metadata takes no part.

#Prereleases and ranges

#Canonical text

#How it compares

#CLI

moon run bin -- parse 1.2.3 v2.0.0-rc.1+build
moon run bin -- compare 1.0.0-rc.1 1.0.0
moon run bin -- sort 2.0.0 1.0.0-beta 1.0.0 0.9.9
moon run bin -- bump prerelease 1.2.3-alpha.1     # 1.2.3-alpha.2
moon run bin -- range "^0.2.3"                    # >=0.2.3, <0.3.0
moon run bin -- range --syntax cargo 1.2.3        # >=1.2.3, <2.0.0
moon run bin -- range --syntax ruby "~> 1.2"      # >=1.2.0, <2.0.0
moon run bin -- satisfies 1.9.0 "^1.2.3"          # true
moon run bin -- max "^1.2.0" 1.0.0 1.2.3 1.5.0    # 1.5.0
moon run bin -- parse --json 1.2.3-alpha.1

{
  "input": "1.2.3-alpha.1",
  "normalised": "1.2.3-alpha.1",
  "major": "1",
  "minor": "2",
  "patch": "3",
  "prerelease": ["alpha", "1"],
  "build": [],
  "is_prerelease": true
}

#Consuming it as a library

let j = @json.to_json(@moonsver.Range::parse("^1.2.3"))
// Json::string(">=1.2.3, <2.0.0")

#Examples and tests

moon run examples   # the smallest useful example
moon test           # 47 cases, green on wasm-gc, js, native and wasm
moon check          # no warnings

#Deliberately not done

• PEP 440. Not SemVer; 1.0.0.post1, ~=1.4 and ==1.* are refused.
• Loose mode. node-semver's loose lets 01.2.3 and 1.2.3beta through. moonsver offers different grammars, not a licence to accept broken input.
• Range algebra. subset, intersects, minVersion and coerce are not here. They are not parsing problems but interval arithmetic over comparator sets, and deserve a module of their own.
• Some Ruby spellings. ~>, != and the comparators all work, but Ruby's bare 1.2 means exactly 1.2.0 (Ruby pads the missing segments with zeroes), which is not npm's x-range. Under the ruby preset that form is refused rather than guessed at — it is a grey area, and guessing would be worse.
• Upper bounds under Always. npm appends -0 to upper bounds (<2.0.0-0) to shut out the next version's prereleases. SameTuple gets the same result and keeps the bounds clean; with Always those prereleases do fall inside, which is what Always means.