npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

version-parser

v0.0.2

Published

This package can parse and compare semantic versioning.

Downloads

9

Readme

Version Parser

Python Version

https://pypi.org/project/version-parser/

JavaScript

The version parser is able to parse versions and figure out which of them are build in one of the following three formats: Major-Version, Minor-Version and Build-Version.

Possible input types are:

| Version | Typ | |----------|-------------------| | v1.2.3 | Version | | V1.2.3 | Version | | v_1_2_3 | FILENAME | | v1_2_3 | FILENAME | | V_1_2_3 | FILENAME | | V1_2_3 | FILENAME | | 1_2_3 | FILENAME | | VM1m2b3 | CLASSNAME_BUILD | | VM1m2p3 | CLASSNAME_PATCH | | vM1m2b3 | CLASSNAME_BUILD | | vM1m2p3 | CLASSNAME_PATCH | | 1.2.3 | STRIPPED_VERSION | | 2312 | NUMBER |

Install

npm install version-parser

Usage

Create object with the version as a String as initial parameter.

const version_parser = require("version-parser");

v1 = new version_parser.Version("v2.3.4")

To compare two version objects/numbers, simply put the versions as Strings into seperate objects and compare them using the logical operators.

const version_parser = require("version-parser");

v1 = new version_parser.Version("v2.3.4")
v2 = new version_parser.Version("v2.3.2")

console.log(v1.lt(v2))
>> False


console.log(v1.gt(v2))
>> True


console.log(v1.eq(v2))
>> False

The last digets behind the last dot should be the Patch or Build Version Number. Differences in this area should be compatible to each other.

const version_parser = require("version-parser");


v1 = new version_parser.Version("v2.3.4")
v2 = new version_parser.Version("v2.3.5")


console.log(v1.eq(v2))
>> False


console.log(v1.compatible_version_with(v2))
>> True

You can also get only the Major, Minor or Build Version by using:

const version_parser = require("version-parser");
v = new version_parser.Version("v2.3.4")

v.get_major_version()
2
v.get_minor_version()
3
v.get_build_version()
4

It's possible to convert the version format, too:

const version_parser = require("version-parser");
v = new version_parser.Version("v2.3.4"); //       # VersionType = Version
console.log(v.get_type())
>> VersionType.Version

console.log(v.get_typed_version(new version_parser.VersionType.FILENAME))
>> v_2_3_4

Any version can be represented by an Integer.

The sections of major, minor, build/patched version should have a maximum of three digets.

const version_parser = require("version-parser");

v = new version_parser.Version("v2.3.4")
console.log(v.get_number())
>> 2003004

VersionTypes

VersionType.FILENAME

"v_<MAJOR>_<MINOR>_<BUILD/PATCH>"

VersionType.CLASSNAME

"VM<MAJOR>m<MINOR>b<BUILD/PATCH>"

VersionType.VERSION

"v<MAJOR>.<MINOR>.<BUILD/PATCH>"

VersionType.STRIPPED_VERSION

"<MAJOR>.<MINOR>.<BUILD/PATCH>"

VersionType.NUMBER

each section is filled zeros up to three digets

"<MAJOR><MINOR><BUILD/PATCH>"

VersionType.CLASSNAME_BUILD

same like CLASSNAME_BUILD

VersionType.CLASSNAME_PATCH

"VM<MAJOR>m<MINOR>p<BUILD/PATCH>"
                  ^
                PATCH