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 🙏

© 2025 – Pkg Stats / Ryan Hefner

npj

v1.0.4

Published

Node Package Jumper: a global cli for javascript natives.'

Readme

NPJ

npj (npm jumper) acts as a global bridge between all your npm projects.

Installation

npm i -g https://github.com/austinbillings/npj.git

Overview

npj makes use of a per-user local "registry" to keep track of which NPM packages are in development are in development where on your machine. This also allows it to easily run scripts from any registered package, triggerable from any directory on your system.

The file used by npj to store your registry lives at ~/.npj-registry, and its contents are a plain JSON object which maps projectName keys to packageDirPath values.

Usage

See help

npj --help

Register a package

cd my-project # anything with a package.json will do
npj add
[NPJ] ✓ OK:    my-project -> /Users/admin/code/my-project @0.0.1

Show registered packages

npj ls
[NPJ] «package»  my-project @0.0.1
[NPJ] >>>>       -->--> /Users/admin/code/my-project

Add another package

cd ../some-other-project
npj add
[NPJ] ✓ OK:    some-other-project -> /Users/admin/code/some-other-project @1.0.3

Listing packages afterward (npj ls):

[NPJ] «package»  my-project @0.0.1
[NPJ] >>>>       -->--> /Users/admin/code/my-project
[NPJ] «package»  some-other-project @1.0.3
[NPJ] >>>>       -->--> /Users/admin/code/some-other-project

Remove from registry

cd my-project
npj remove
[NPJ] ✓ OK:    Removed "some-other-project" from registry

List scripts offered by a registered package

npj scripts my-package
[NPJ] «package»  my-package @0.0.1
[NPJ] >>>>       -->--> /Users/admin/code/my-package
[NPJ] «script»   test
[NPJ] >>>>          node tests/all.js
[NPJ] «script»   build
[NPJ] >>>>          node build.js

Run a registered package's script (or multiple!)

When multiple <packageName>:<scriptName> sets are provided, they are run in sequence (not parallel!)

npj my-project:build my-project:test
[NPJ] «script»   my-project: Running script «build»

> [email protected] build /Users/admin/code/my-project
> node build.js
...
[NPJ] «script»   script process exited with code 0
[NPJ] «script»   my-project: Running script «test»

> [email protected] test /Users/admin/code/my-project
> node tests/all.js
...
[NPJ] «script»   script process exited with code 0