WHAT IT DOES
Check the range before the package manager resolves it.
Enter one or more strict semantic versions and an npm-style range such as ^2.4.0, ~1.8.3, or >=1 <3. Each version is normalized and tested with node-semver, the same rules used throughout the npm ecosystem. When exactly two versions are entered the result also states their precedence, including prerelease identifiers, without treating build metadata as an ordering signal.
Why use it?
Use it to check exactly which releases an npm-style dependency constraint admits, especially around major-zero and prerelease versions.
How to use this tool
- Enter the range and one complete version per line, or load the built-in example.
- Test ^2.4.0 against 2.4.0, 2.9.0, and 3.0.0: the first two satisfy it and 3.0.0 does not.
- Review prerelease handling and any explicit Include prerelease setting. A satisfying version is a range match, not a claim that the release is compatible or available in a registry.
Details and limitations
- Versions must contain major, minor, and patch components so a shorthand range is never mistaken for a complete release identifier.
- Ranges support comparator sets, hyphen ranges, tilde, caret, wildcards, logical OR, and prerelease comparators under node-semver semantics.
- Prereleases remain excluded from ordinary ranges unless the range names a prerelease or the explicit Include prerelease option is enabled.
- The normalized range and its lowest satisfiable version are shown beside the per-version verdicts.