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

npmbrew

v1.5.3

Published

a npm version manager

Downloads

74

Readme

npmbrew -- a npm version manager

Build Status NPM Downloads

Why npmbrew?

npm is flooded with issue reports on a daily basis. Sometimes I spent just too much time juggling around different npm versions trying to reproduce the error.

I created npmbrew to make it easy to switch versions. See also: #14

Install

Using npm.

npm install -g npmbrew

Usage

Usage: npmbrew <command>

Commands:
clean                Delete all installed sources
help                 Output help information
install <version>    Install the version passed
ls                   List versions currently installed
ls-remote            List registry versions
npm                  An alias of npm <command>
uninstall <version>  Delete the install for <version>
use <version>        Use <version>

Example

Install

npmbrew install v2.6.0
installed

Switch version with use:

npmbrew use v2.6.0
Using v2.6.0

Use npm

npmbrew npm help
Usage: npm <command> blah blah...

Add npmbrew npm to PATH

Add the following line to the end of your .bashrc or .zshrc.

# npmbrew
export PATH=$HOME/.npmbrew/current/bin:$PATH

Reload config.

source ~/.zshrc

Test.

npm help
Usage: npm <command> blah blah...

One more thing

npmbrew uses update-notifier, to let users know when there is a new version available for download.

npm whoami
watilde


┌──────────────────────────────────────────┐
│ Update available: 2.7.0 (current: 2.6.0) │
│ Run npmbrew install 2.7.0 to update.     │
└──────────────────────────────────────────┘

LICENSE

The MIT License (MIT)

Copyright (c) 2015 Daijiro Wachi

See also: LICENSE.