Semver Parser

Online tool for parsing semver versions, prerelease, build metadata, and ranges from package.json.

Обработка выполняется локально в браузере. Данные не отправляются на сервер.

For this tool, processing runs locally in your browser and data is not sent to the server.

Semver Parser is a free online tool for understanding Semantic Versioning structure from package.json, changelog, and dependency ranges. Processing runs locally in your browser.

What it does

Output

Processing

Continue working

Choose a related tool for the next step.

Data passed between tools is kept only in the current browser session.

How to use

Choose mode: parse version, parse semver range, or compare two versions.
Enter a version such as 1.2.3 or 1.2.3-beta.1, or a range from package.json: ^1.2.3, ~1.2.3, >=1.2.0 <2.0.0.
Review major, minor, patch, prerelease, build metadata, range bounds, or comparison result.
Copy the result for releases, package.json, documentation, changelog, or upgrade discussions.

More about this tool

Semver Parser helps understand Semantic Versioning structure: major, minor, patch, prerelease, and build metadata.

Useful for npm packages, package.json, changelog, releases, dependency ranges, and library updates. Parse version 1.2.3, prerelease 1.2.3-beta.1, build metadata, caret range ^1.2.3, tilde range ~1.2.3, comparator range >=1.2.0 <2.0.0, and compare two versions.

The service does not contact npm registry or check latest package versions.

Processing runs locally in your browser.

Parses major, minor, and patch
Shows prerelease and build metadata
Explains caret and tilde ranges
Helps understand package.json conditions
Compares two semver versions
Runs in the browser
Data is not sent to the server
No registration required

Frequently Asked Questions

What is semver?

Semver, or Semantic Versioning, is a version format major.minor.patch, e.g. 1.2.3. Major usually means breaking changes, minor new compatible features, patch fixes.

What do major, minor, and patch mean?

Major is the first part, minor the second, patch the third. In 2.5.1, major is 2, minor is 5, patch is 1.

What is prerelease?

Prerelease is a pre-release version such as 1.2.3-beta.1. It usually ranks lower than stable 1.2.3.

What is build metadata?

Build metadata comes after +, e.g. 1.2.3+build.5. It does not affect semver comparison order.

What does ^1.2.3 mean in package.json?

Usually ^1.2.3 means compatible versions from 1.2.3 inclusive to 2.0.0 exclusive. Rules are stricter for 0.x versions.

What does ~1.2.3 mean?

Usually ~1.2.3 means patch updates from 1.2.3 inclusive to 1.3.0 exclusive.

Why are 0.x versions special?

In semver, major 0 often means unstable API. Ranges like ^0.2.3 usually allow a narrower update range than ^1.2.3.

Can two versions be compared?

Yes. In compare mode enter two semver versions and see which is newer and the change type: major, minor, patch, or prerelease.

Does the service check latest npm package version?

No. This tool parses semver strings locally. Checking npm registry and latest versions is a separate task.

Is my data sent to the server?

No. Processing runs locally in your browser and data is not sent to the server.

Do I need to register?

No. The tool works without registration.

How to use

Choose mode: parse version, parse semver range, or compare two versions.

Enter a version such as 1.2.3 or 1.2.3-beta.1, or a range from package.json: ^1.2.3, ~1.2.3, >=1.2.0 <2.0.0.

Review major, minor, patch, prerelease, build metadata, range bounds, or comparison result.

Copy the result for releases, package.json, documentation, changelog, or upgrade discussions.

More about this tool

Semver Parser helps understand Semantic Versioning structure: major, minor, patch, prerelease, and build metadata.

The service does not contact npm registry or check latest package versions.

Processing runs locally in your browser.

Parses major, minor, and patch
Shows prerelease and build metadata
Explains caret and tilde ranges
Helps understand package.json conditions
Compares two semver versions
Runs in the browser
Data is not sent to the server
No registration required

Frequently Asked Questions

What is semver?

Semver, or Semantic Versioning, is a version format major.minor.patch, e.g. 1.2.3. Major usually means breaking changes, minor new compatible features, patch fixes.

What do major, minor, and patch mean?

Major is the first part, minor the second, patch the third. In 2.5.1, major is 2, minor is 5, patch is 1.

What is prerelease?

Prerelease is a pre-release version such as 1.2.3-beta.1. It usually ranks lower than stable 1.2.3.

What is build metadata?

Build metadata comes after +, e.g. 1.2.3+build.5. It does not affect semver comparison order.

What does ^1.2.3 mean in package.json?

Usually ^1.2.3 means compatible versions from 1.2.3 inclusive to 2.0.0 exclusive. Rules are stricter for 0.x versions.

What does ~1.2.3 mean?

Usually ~1.2.3 means patch updates from 1.2.3 inclusive to 1.3.0 exclusive.

Why are 0.x versions special?

In semver, major 0 often means unstable API. Ranges like ^0.2.3 usually allow a narrower update range than ^1.2.3.

Can two versions be compared?

Yes. In compare mode enter two semver versions and see which is newer and the change type: major, minor, patch, or prerelease.

Does the service check latest npm package version?

No. This tool parses semver strings locally. Checking npm registry and latest versions is a separate task.

Is my data sent to the server?

No. Processing runs locally in your browser and data is not sent to the server.

Do I need to register?

No. The tool works without registration.