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

@mtoledo/semver-check

v1.0.1

Published

A tool to determine if a version satisfies a semver range. This tool is also able to list versions of existing node modules that match a semver range.

Downloads

14

Readme

semver-check

A tool to determine if a version satisfies a semver range. This tool is also able to list versions of existing node modules that match a semver range.

Why?

Trying to decipher the semver rules made my eyes gloss over. I learn better by experimentation. Creating and using this command line node tool helped me grock just how semver works.

Installation

npm i -g @mtoledo/semver-check

Usage

Usage: semver-check [options] [command]

A tool to determine if a version satisfies a semver range. This tool is also able to list versions of existing node modules that match a semver range.

Options:
  -V, --version                           output the version number
  -h, --help                              display help for command

Commands:
  filter [options] <packageName> <range>
  List all the versions of <packageName> that are satisfied by a semver <range>. Example `filter commander ^1.0.0`

  test <version> <range>
  Test to see if a version number satisfies a semver range.

  help [command]                          display help for command

Examples

See which versions of a React satisfy the semver range of ^16.0.0

$> semver-check filter react ^16.0.0

✅ The following versions of react satisfy the semver range of ^16.0.0:
 16.0.0, 16.1.0, 16.1.1, 16.2.0, 16.3.0, 16.3.1, 16.3.2, 16.4.0, 16.4.1, 16.4.2, 16.5.0, 16.5.1, 16.5.2, 16.6.0, 16.6.1, 16.6.2, 16.6.3, 16.7.0, 16.8.0, 16.8.1, 16.8.2, 16.8.3, 16.8.4, 16.8.5, 16.8.6, 16.9.0, 16.10.0, 16.10.1, 16.10.2, 16.11.0, 16.12.0, 16.13.0, 16.13.1, 16.14.0

Get those results in json format with some metadata.

$> semver-check filter -j react ^16.0.0

{"packageName":"react","range":"^16.0.0","validVersions":["16.0.0","16.1.0","16.1.1","16.2.0","16.3.0","16.3.1","16.3.2","16.4.0","16.4.1","16.4.2","16.5.0","16.5.1","16.5.2","16.6.0","16.6.1","16.6.2","16.6.3","16.7.0","16.8.0","16.8.1","16.8.2","16.8.3","16.8.4","16.8.5","16.8.6","16.9.0","16.10.0","16.10.1","16.10.2","16.11.0","16.12.0","16.13.0","16.13.1","16.14.0"]}

Test if a supplied version satisfies a semver range

semver-check test 1.0.0-alpha.1 ^1.0.0-alpha.0
✅ The version "1.0.0-alpha.1" satisfies the semver range "^1.0.0-alpha.0"
semver-check test 1.0.0-alpha.1 ^1.0.0-beta.0
❌ The version  "1.0.0-alpha.1" falls outside of the semver range "^1.0.0-beta.0"

It's wise to put quotes around semver ranges that use symbols that have a special meaning to your shell, like the tilde

$> semver-check test 1.0.0-alpha.1 ~1.0.0
zsh: no such user or named directory: 1.0.0
semver-check test 2.0.0  "~2.0.0"
✅ The version "2.0.0" satisfies the semver range "~2.0.0"