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

npm-show-versions

v1.0.3

Published

Show important package availability information

Downloads

4

Readme

npm-show-versions

$ npm-show-versions semver
$ npm-show-versions semver@2

npm-show-versions packagename[@packageversion]

A small tool to show which versions of a package would match a particular version string for your copy of node and npm. It takes into account not just package version, but also engine restrictions and engineStrict.

So for instance, on node 0.11.x:

$ npm-show-versions abraxas@2
Name: abraxas
Description: A streaming gearman client / worker / server (as you choose)
Versions:
* 2.1.0 [latest] (requires: node >= 0.10.0)
* 2.0.2  (requires: node >= 0.10.0)
! 2.0.1  (suggests: node! ~0.10.0)
  2.0.0  (requires: node! ^0.10.0)
  1.2.1  (requires: node! ^0.10.0)
  1.2.0  (requires: node! ^0.10.0)
  1.1.0  (requires: node! ^0.10.0)
  1.0.0  (requires: node! ^0.10.0)
  0.4.0
  0.3.1
  0.3.0
  0.2.1
  0.2.0
  0.1.0

The * in the first column means that the package can be installed and meets all criteria. The ! in the first column means the package can be installed but there will be warnings. The node! in the suggests/requires section means that's the requirement that's failing. And finally anything in square brackets, like [latest], shows the version a tag is associated with. All modules at a minimum have a latest tag.