Microdeck.tools 100% In-Browser

SemVer Range & npm Version Tester

New

Validate package version constraints using the canonical `semver` spec engine. Check which candidate versions satisfy expressions like `^1.2.0` or `>=2.0.0 <2.5.0`, inspect `minSatisfying` / `maxSatisfying`, compare two releases (`major`/`minor`/`patch` diff), and preview next bumped version strings.

100% In-Browser No Server Storage Instant Results

npm SemVer Range Matcher

Normalized: >=1.2.0 <2.0.0-0Max: 1.9.2Min: 1.2.4
0.9.8excluded
1.0.0excluded
1.2.4satisfies
1.5.0-alpha.1excluded
1.5.0satisfies
1.9.2satisfies
2.0.0excluded
2.1.0excluded

Compare Two Versions

1.4.2 is older than 1.5.0-rc.1
Release diff: preminor

Bump Release Calculator

patch: 1.4.3
minor: 1.5.0
major: 2.0.0
pre: 1.4.3-beta.0

Did this tool save you time? Help keep Microdeck free and maintained. Completely optional · From $3.

How It Works Under the Hood

Powered directly by the standard `semver` package used by npm itself, the tester parses comparator sets (`^`, `~`, hyphen ranges, `||` unions), checks each version with optional prerelease inclusion, sorts matching releases, and exposes `semver.compare`, `semver.diff`, and `semver.inc`.

Step-by-Step Instructions

1

Enter an npm version range expression such as `^1.2.0` or `>=1.4.0 <2.0.0`.

2

Paste candidate package versions (one per line or comma-separated) and toggle prerelease inclusion if needed.

3

Inspect normalized range bounds, highest `maxSatisfying` match, and pass/exclude tags per version.

4

Use the lower cards to compare two exact versions or preview `patch`, `minor`, `major`, and `prerelease` bumps.

Key Features & Performance

  • Authentic npm `semver` resolution guarantees exact parity with `package.json` and lockfile behavior
  • Computes `maxSatisfying` and `minSatisfying` across arbitrary candidate lists instantly
  • Side-by-side two-version comparator reports exact release difference (`major`, `minor`, `patch`, `prerelease`)
  • Interactive version bump calculator previews `patch`, `minor`, `major`, and named prerelease increments (`alpha`/`beta`/`rc`)
  • Runs entirely client-side with zero registry polling needed

Methodology, Formulas & Technical Standards

Follows SemVer 2.0.0 and npm node-semver precedence rules, including `0.x.y` caret behavior (`^0.2.3` translates to `>=0.2.3 <0.3.0`) and strict prerelease opt-in gating.

Common Real-World Use Cases

  • Verifying whether `^0.14.0` accidentally permits breaking `0.15.0` upgrades in `package.json`
  • Testing complex compound ranges (`>=18.0.0 <20.0.0 || ^20.11.0`) before changing `engines.node`
  • Computing exact next prerelease tags (`1.4.2 -> 1.4.3-beta.0`) during CI/CD release dry runs
  • Settling version ordering debates (`1.5.0-rc.1` vs `1.5.0`) objectively

Worked Examples & Edge Cases

Zero-Major Caret Behavior

Input
Range: ^0.2.3 | Candidates: 0.2.9, 0.3.0
Output
Matches: 0.2.9 (maxSatisfying) | Excluded: 0.3.0

In `0.x.y`, caret locks the minor digit because breaking changes happen in minor bumps.

Prerelease Precedence

Input
Left: 1.4.2 | Right: 1.5.0-rc.1
Output
1.4.2 is older than 1.5.0-rc.1 (diff: premajor/preminor)

Prerelease comes before `1.5.0` final, after `1.4.2`.

Limitations, Scope & Accuracy Notes

  • • Evaluates SemVer 2.0.0 / npm syntax; Python PEP 440 (`~=`) or Cargo-specific variations outside standard SemVer require manual translation.
  • • Does not query remote npm registries so offline privacy is preserved.

Local Browser Processing & Privacy

Traditional web converters upload your documents, snippets, or media files to remote servers. SemVer Range & npm Version Tester runs inside your browser tab:

Processed in This Tab

Your input text and files are processed locally without uploading payloads to a processing server.

No Tool Payload Logging

Microdeck does not log or store the files or inputs you paste into tool workspaces (normal static hosting/CDN requests still load page assets).

Tab Memory Lifecycle

Working outputs stay in your browser tab and are released when you reset the tool or close the tab.

Frequently Asked Questions

Why does `^1.2.0` ignore `1.5.0-alpha.1` by default?

Per npm SemVer rules, prerelease versions do not match comparators unless the comparator explicitly shares the same `[major, minor, patch]` tuple or prerelease mode is toggled on.

What is the difference between `~1.2.3` and `^1.2.3`?

Tilde `~1.2.3` allows patch updates (`<1.3.0`), whereas caret `^1.2.3` allows minor and patch updates (`<2.0.0`).

Does this support `||` union ranges?

Yes. Expressions like `^16.0.0 || ^18.0.0` evaluate natively through `semver.validRange`.

Are trailing build metadata tags (`+build.42`) ignored in precedence?

Yes. Per SemVer 2.0.0 §10, build metadata does not affect version ordering.

Explore Related Micro-Tools

Support Microdeck

Completely optional · From $3 · No account required

Choose an amount (USD):Selected:$5

Minimum support amount is $3 USD.

Completely optional · From $3 · Checkout opens on Gumroad.