Semver Calculator

Semantic versions ko apne browser mein parse, compare, range-check, increment aur coerce karein. Aap jo versions type karte hain woh aapke device par rehte hain.

Aap jo versions aur ranges enter karte hain woh locally aapke browser mein evaluate hote hain aur kabhi upload nahi hote.

Ek quick unique id chahiye? UUID Generator try karein.

Semver Calculator ke baare mein

Yeh semver calculator version numbers ke saath aap jo bhi karte hain uske liye ek Semantic Versioning toolkit hai. 1.2.3-beta.1+build.42 jaise version ko uske major, minor, patch, prerelease aur build metadata mein parse karein; do versions compare karke dekhein kaun naya hai aur kis level par farak hai; check karein ki koi version ^1.2.3, ~1.2, 1.x, ya >=1.0.0 <2.0.0 jaise npm range ko satisfy karta hai ya nahi; ek version ko major, minor, patch, ya kisi bhi prerelease step se increment karein; aur v1.2 jaisi loose string ko ek clean semver mein coerce karein. Yeh un developers, package authors aur release engineers ke liye banaya gaya hai jo har roz dependency ranges ke baare mein sochte hain. Wahi semver library se powered jo npm use karta hai, har calculation aapke browser mein chalti hai isliye aap jo versions type karte hain woh aapke device par rehte hain.

Features

Semver Calculator kaise use karein

  1. Ek mode pick karein: Parse, Compare, Range, Increment, ya Coerce.
  2. Ek version type karein (aur mode ke hisaab se ek doosra version ya ek range).
  3. Inputs ke neeche info rows aur badges mein live results padhein.
  4. Jo value chahiye use copy karein, jaise bumped version ya diff level.

Example

Input

version: 1.5.0
range:   ^1.2.3

Output

1.5.0 satisfies ^1.2.3  ✓
1.6.0 → pass   2.0.0 → fail

Ek caret range ^1.2.3 agle major (2.0.0) tak, par use shaamil kiye bina, kuch bhi allow karta hai.

Common errors aur troubleshooting

Aksar pooche jaane wale sawaal

^1.2.3 range kya allow karta hai?
Ek caret range ^1.2.3 koi bhi aisa version allow karta hai jo left-most non-zero digit ko nahi badalta, isliye yeh 1.2.3 se 2.0.0 tak (par use shaamil kiye bina) match karta hai. 0.x versions ke liye rules sakht ho jaate hain: ^0.2.3, 0.2.3 se 0.3.0 tak allow karta hai.
Ek prerelease version ko stable release se kaise compare kiya jaata hai?
Ek prerelease ki precedence apne associated release se kam hoti hai, isliye 1.0.0-rc.1, 1.0.0 se kam hai. Prereleases field dar field compare hote hain: identifiers sort hote hain, aur numeric identifiers longer ya alphanumeric wale se neeche rank karte hain.
~1.2 aur ^1.2 mein kya farak hai?
Tilde ~1.2, 1.2 ke andar patch-level changes allow karta hai (>=1.2.0 <1.3.0), jabki caret ^1.2 agle major tak minor aur patch changes allow karta hai (>=1.2.0 <2.0.0). Sample versions pass ya fail dekhne ke liye Range mode use karein.
Yeh semver calculator build metadata kaise handle karta hai?
Plus sign ke baad build metadata (jaise +build.42) parse aur dikhaya jaata hai, par precedence compare karte waqt use ignore kiya jaata hai, isliye 1.0.0+a aur 1.0.0+b equal versions maane jaate hain.
Ek version ko coerce karna kya karta hai?
Coercion ek loose string ko valid semver mein badalta hai, jitna ho sake pehla major.minor.patch sequence dhoondhkar. Isliye v1.2 banta hai 1.2.0, 1.2.3.4 banta hai 1.2.3, aur release-3.1 banta hai 3.1.0; missing parts default mein zero ho jaate hain.
Main kaun se release types se increment kar sakta hoon?
Aap major, minor, patch, premajor, preminor, prepatch, ya prerelease se bump kar sakte hain. pre- variants chune hue part par ek prerelease line shuru karte hain, jaise 1.2.3 par ek premajor 2.0.0-0 deta hai.

Related tools

Saare ArrayKit tools