Semver 範囲テスター

セマンティックバージョン範囲が指定バージョンに一致するかテストします。

1行に1バージョン

3/8 一致
1.0.0不一致
1.2.3一致
1.2.4一致
1.9.9一致
2.0.0不一致
2.0.0-beta.1不一致
2.1.0不一致
3.0.0不一致

範囲構文リファレンス

^1.2.3Compatible: >=1.2.3 <2.0.0
~1.2.3Patch-level: >=1.2.3 <1.3.0
>=1.0.0 <2.0.0Range (AND)
1.0.0 || 2.0.0Union (OR)
1.2.3 - 2.3.4Hyphen range (inclusive)
*Any version

What Is the Semver Range Tester?

The semver range tester checks whether a list of semantic version numbers satisfy a given version range. Enter a range expression like ^1.2.3 or >=1.0.0 <2.0.0, paste your versions, and see instantly which ones match.

This is useful for debugging package.json dependency ranges, understanding npm/yarn resolution, and verifying that a version constraint covers the versions you expect.

How to Use the Semver Range Tester

  1. Enter a version range in the input field, or click one of the preset examples.
  2. Enter one or more version numbers in the textarea, one per line.
  3. Results appear instantly — green checkmark for a match, red cross for no match.
  4. Invalid version strings (not valid semver) are shown with a strikethrough.

Features

  • Supports all common range operators: ^, ~, >, >=, <, <=, =
  • Hyphen ranges: 1.0.0 - 2.0.0
  • AND ranges: >=1.0.0 <2.0.0 (space-separated)
  • OR ranges: 1.0.0 || 2.0.0
  • Wildcard: *
  • Pre-release version support: 1.0.0-beta.1
  • Batch test — paste many versions at once
  • Built-in syntax reference card

FAQ

What does the caret (^) mean in semver ranges?

The caret ^ allows changes that do not modify the left-most non-zero digit. ^1.2.3 matches >=1.2.3 <2.0.0. ^0.2.3 matches >=0.2.3 <0.3.0. It is the default range operator used by npm install.

What does the tilde (~) mean in semver ranges?

The tilde ~ allows patch-level changes. ~1.2.3 matches >=1.2.3 <1.3.0. It is more restrictive than ^ and is useful when you want to allow bug fixes but not new minor features.

What is semantic versioning (semver)?

Semantic versioning is a versioning scheme with the format MAJOR.MINOR.PATCH. MAJOR increments for breaking changes, MINOR for new backwards-compatible features, and PATCH for backwards-compatible bug fixes. Pre-release versions use a hyphen suffix like 1.0.0-beta.1.

How do I test multiple version ranges at once?

Use the OR operator (||) to combine ranges: 1.0.0 || 2.0.0 matches exactly those two versions. For a continuous range, use >=1.0.0 <3.0.0 or the hyphen syntax 1.0.0 - 2.9.9.