Developer tools
Semantic Version Range Tester
Check which versions satisfy a release range before selecting a dependency.
Processed locally. Your input and output are never uploaded.
Tool overview
How Semantic Version Range Tester works
Semantic Version Range Tester evaluates one version per line against common npm-style range operators and keeps invalid versions visible. It keeps input and output separate, runs locally, and documents boundaries instead of making unsupported guarantees.
Dependency range decisions
- evaluates one version per line against common npm-style range operators and keeps invalid versions visible. for a repeatable local workflow
- Review pasted or locally opened data before copying it
- Prepare output for a related PasteTidy tool
Test a list against a range
- Paste the source or open a supported local file.
- Choose the documented options and review the separate result.
- Copy or download only after checking the visible output.
Comparators, prereleases, and wildcards
- Version range: Common range such as ^1.2.0 or >=1.0.0 <2.0.0.
- Include prereleases: Allow prereleases when the range permits them.
Find versions matching a caret range
Before
1.2.0 1.5.0 2.0.0 1.3.0-beta.1
After
1.2.0 yes yes 1.5.0 yes yes 2.0.0 yes no 1.3.0-beta.1 yes no
Supported range subset
- Only the documented common range subset is implemented; every package-manager dialect is not implied.
- Large input is bounded by the documented local worker limits.
- Input, options, and output are not sent to analytics or placed in URLs.
Browse all developer tools tools โ
Questions
Semantic Version Range Tester FAQ
Does Semantic Version Range Tester upload my input?
No. Processing stays in the current browser tab or its local Web Worker.
Is the result authoritative?
No. Review the output and the documented limitations before using it in a production workflow.