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

pkg-version

v0.2.0

Published

List a package's dependencies and installed versions

Downloads

3

Readme

pkg-version

One of the problems with using semver ranges is that you can inadvertently end up with a newer version of one of your dependencies, which can in turn break things. This is where you get into the argument between co-workers "Well, it works on my machine!".

This module is meant to help identify what's different between the version package.json is asking for, and what is actually installed. By highlighting the version difference between what you have installed, and what you thought you had installed, you can narrow down what package, and what version introduced the breaking change.

Installation

$ npm install -g pkg-version

Synopsis

$ pkg-version [<folder>] [<options>]
  • <folder>: A folder containing a package.json file (defaults to current directory).

Options:

  • -a Include all dependencies (default).
  • -s Include all dependencies that appear in dependencies.
  • -d Include all dependencies that appear in devDependencies.
  • -p Include all dependencies that appear in peerDependencies.

Usage

Show dependencies for a package and highlight version differences.

$ pkg-version
Package                     Wanted   Actual
babel                       ^5.5.8    5.8.3
babel-core                  ^5.5.6    5.8.3
babel-eslint               ^3.1.23   3.1.24
babel-loader                ^5.1.4    5.3.2
eslint                     ^0.24.1   0.24.1
karma                     ^0.12.36  0.12.37
karma-chrome-launcher      ^0.1.12   0.1.12
karma-cli                    0.0.4    0.0.4
karma-firefox-launcher      ^0.1.6    0.1.6
karma-mocha                ^0.1.10   0.1.10
karma-sourcemap-loader      ^0.3.5    0.3.5
karma-webpack               ^1.5.1    1.6.0
mocha                       ^2.2.5    2.2.5
webpack                    ^1.9.10   1.10.1
webpack-dev-server          ^1.9.0   1.10.1

License

MIT