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

conver

v1.2.0

Published

Comparisons for concrete semantic versions (i.e. compare 1.2.3 instead of ^1.2.3)

Downloads

14

Readme

conver

Comparisons for concrete semantic versions (i.e. compare 1.2.3 instead of ^1.2.3).

Motivation

semver is a great implementation of semantic versioning; including all the edge cases. These edge cases are important in many scenarios, but often we are simply comparing two concrete versions (i.e. compare 1.2.3 instead of ^1.2.3).

In this more limited use-case case including all 1000+ lines of semver into your bundle for a web application is a bit of overkill. conver aims to do ONLY concrete version comparisons in a drastically smaller package size (currently 28 LOC excluding comments).

Usage

conver exposes the same comparison methods you would expect from the semver package. Specifically:

  • gt(v1, v2): returns true if v1 is greater than v2.
  • lt(v1, v2): returns true if v1 is less than v2.
  • equal(v1, v2): returns true if v1 is equal to v2.
  • compare(v1, v2) returns 0 if v1 == v2, or 1 if v1 is greater, or -1 if v2 is greater.
  • parse(v1): returns an array of [major, minor, patch, build]
  • stringify(src): returns a string representation of the specified src – an Array of [major, minor, patch, build].
conver.gt('3.4.5', '1.2.3'); // true
conver.gt('1.2.3', '3.4.5'); // false

conver.lt('1.2.3', '3.4.5'); // true
conver.lt('3.4.5', '1.2.3'); // false

conver.eq('1.2.3', '9.8.0'); // false
conver.eq('1.2.3', '1.2.3'); // true

conver.parse('1.2.3');       // [1, 2, 3, '']
conver.parse('1.2.3-alpha'); // [1, 2, 3, 'alpha']

conver.stringify([1, 2, 3, 'alpha']); // '1.2.3-alpha'
conver.stringify([1, 2, 3]);          // '1.2.3'
conver.stringify([1, 2]);             // '1.2'
conver.stringify([1]);                // '1'

Test

Tests are written with nyc, assume, and mocha. They can be run with npm:

npm test
LICENSE: MIT
AUTHOR: Charlie Robbins