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 🙏

© 2026 – Pkg Stats / Ryan Hefner

nme

v1.0.11

Published

Node Modules Extravaganza - Allows you to easily switch between many node_modules installation folders.

Readme

Node Modules Extravaganza

Allows you to easily switch between many node_modules installation folders.

npm install -g nme

Usage

nme ?

How it works

Creates a .nme folder in your current working directory, where node_modules folders will be named and stored.

Node modules folders managed by nme will contain a .nme.json file that will contain the name.

This way when the folder is activated (renamed to node_modules and moved out of the storage directory) the name is retained for future storage.

nme uses "move" command not "copy"

Examples

nme store pre-upgrade-modules will backup your current installation

nme install new-upgraded-modules will backup your current install and run npm install and name your new install new-upgraded-modules

if your current install is un-named - a name will be generated in the format unnamed-installation001

Managing installed versions

nme list will show your active version

nme use _____ will swap your current version for the one specified in _____

Renaming an installed version

currently the only way to rename an installed version is to store it with a new name, then use the new name

this can be useful if you run npm install and the current name no longer reflects the current install state.

instead you might use nme install new-updates to backup your current installation (if exists) and tag your new installation with a name

Removing old versions

ls .nme will show your old versions, and you may delete them the same way you would delete any other folder.

rm -fr .nme\old-version-name

Performance notes

Set your text editors to exclude .nme directory from searches and listings

Reason For Existence

Most of the time this shouldn't really be needed

  1. It's nice to have a backup
  2. Manually switching between backup and current version is only fun the first time