- Notifications
You must be signed in to change notification settings - Fork1
watilde/npmbrew
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
npm is flooded withissue 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
Using npm.
npm install -g npmbrewUsage: npmbrew <command>Commands:clean Delete all installed sourceshelp Output help informationinstall <version> Install the version passedls List versions currently installedls-remote List registry versionsnpm An alias of npm <command>uninstall <version> Delete the install for <version>use <version> Use <version>Install
npmbrew install v2.6.0installedSwitch version withuse:
npmbrew use v2.6.0Using v2.6.0Use npm
npmbrew npm helpUsage: npm <command> blah blah...Add the following line to the end of your .bashrc or .zshrc.
# npmbrewexport PATH=$HOME/.npmbrew/current/bin:$PATHReload config.
source ~/.zshrcTest.
npm helpUsage: npm <command> blah blah...npmbrew usesupdate-notifier, to let users know when there is a new version available for download.
npm whoamiwatilde┌──────────────────────────────────────────┐│ Update available: 2.7.0 (current: 2.6.0) ││ Run npmbrew install 2.7.0 to update. │└──────────────────────────────────────────┘The MIT License (MIT)
Copyright (c) 2015 Daijiro Wachi
See also:LICENSE.
About
a npm version manager
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
No releases published
Packages0
No packages published
Uh oh!
There was an error while loading.Please reload this page.