Skip to content

Instantly share code, notes, and snippets.

Created September 20, 2014 19:36
Star You must be signed in to star a gist
Save othiym23/4ac31155da23962afd0e to your computer and use it in GitHub Desktop.
a safe way to upgrade all of your globally-installed npm packages
set -e
set -x
for package in $(npm -g outdated --parseable --depth=0 | cut -d: -f3)
npm -g install "$package"
set -e
set -x
for package in $(npm -g outdated --parseable --depth=0 | cut -d: -f2)
npm -g install "$package"
Copy link

Running npm v6.8.0 and seeing this problem again. Global packages won't update beyond "wanted".

> npm outdated --global
Package        Current  Wanted  Latest  Location
color-convert    1.9.3   1.9.3   2.0.0
mocha            5.2.0   5.2.0   6.0.0
pdfkit           0.8.3   0.8.3   0.9.0

> npm update --global pdfkit
# does nothing

> npm update --global pdfkit@latest
# does nothing

> npm install --global pdfkit
+ pdfkit@0.9.0
added 8 packages from 41 contributors and updated 22 packages in 9.638s

Copy link

If you prefer to choose which global modules are updated I've added interactive updating to npm-check with support for global.

It also includes links to the source for each updated package so you can find out what's new.

Behind the scenes npm-check uses npm install thanks to the recommendation from @othiym23 in this thread.

# install
npm -g i npm-check

# interactive update of global packages
npm-check -u -g

# interactive update for a project you are working on
npm-check -u

Example using npm-check -u:
screen shot 2014-10-20 at 10 39 29 am


Great, bro! Thanks! :D

Copy link

The Wanted version shall be another major version, which is not very favorable, since it can break things.

Here is a way to upgrade only minor versions of global packages:

npm_global_packages=($(npm list -g --depth 0 | awk '/ /{print $2}'))
for val in "${npm_global_packages[@]}"; do
    npm i -g --force $(echo $val | tr "." "\n" | head -1)

more context

Good part is, that it will not bump npm to a version that is incompatible with the current node version, so this will most likely not break.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment