Test a local version list against an npm SemVer range, with explicit prerelease behavior and sorted matches.
Your input
Outputs are cleared when the input changes.
Result
Enter your data or use the example, then run the tool.
Worked example
^0.2.3 matches 0.2.3 and 0.2.9 but not 0.3.0. The sample prerelease is excluded by default and the line “invalid” is marked invalid.
Method
Use the pinned node-semver validRange, valid and satisfies implementations with loose=false. Matches are sorted by the upstream sort function, including its build-metadata tie ordering. No version coercion is used.
Limits
Range up to 1000 characters; list up to 100000 characters/1000 lines, each version up to 256 characters. No npm registry requests, dependency resolution or guarantee that a product follows SemVer. Upstream valid retains its leading-v compatibility behavior.
Processing is local in a lazily loaded, fixed-source worker. Cancel or the four-second processing timeout terminates the worker; input is not sent to external services.
Your inputs stay on this device. Only optional, consented page visits are measured. Input values, files, filenames and processing logs are not sent to Analytics.
When switching languages, text, settings and selected files are temporarily kept on this device. Transfers are removed after restoring; interrupted transfers are cleaned up on a later visit. Inputs and files are never uploaded.