Go to main content

man pages section 1: User Commands

Exit Print View

Updated: Thursday, June 13, 2019

npm-update (1)


npm-update - Update a package


npm update [-g] [<pkg>...]

aliases: up, upgrade


NPM-UPDATE(1)                                                    NPM-UPDATE(1)

       npm-update - Update a package

         npm update [-g] [<pkg>...]

         aliases: up, upgrade

       This  command will update all the packages listed to the latest version
       (specified by the tag config), respecting semver.

       It will also install  missing  packages.  As  with  all  commands  that
       install  packages, the --dev flag will cause devDependencies to be pro-
       cessed as well.

       If the  -g  flag  is  specified,  this  command  will  update  globally
       installed packages.

       If no package name is specified, all packages in the specified location
       (global or local) will be updated.

       As of , thenpm updatewill only inspect top-level packages.  Prior  ver-
       sions ofnpmwould also recursively inspect all dependencies.  To get the
       old behavior, usenpm --depth 9999 update`.

       As of , thenpm updatewill changepackage.jsonto save the new version  as
       the minimum required dependency. To get the old behavior, usenpm update

       IMPORTANT VERSION NOTE: these examples assume or later.  For older ver-
       sions  ofnpm,  you must specify--depth 0` to get the behavior described

       For the examples below, assume that the current package is app  and  it
       depends  on dependencies, dep1 (dep2, .. etc.).  The published versions
       of dep1 are:

           "dist-tags": { "latest": "1.2.2" },
           "versions": [

   Caret Dependencies
       If app's package.json contains:

         "dependencies": {
           "dep1": "^1.1.1"

       Then  npm  update  will  install  ,  because1.2.2islatestand1.2.2satis-

   Tilde Dependencies
       However, if app's package.json contains:

         "dependencies": {
           "dep1": "~1.1.1"

       In this case, running npm update will install .  Even though thelatest-
       tag points to1.2.2, this  version  does  not  satisfy~1.1.1,  which  is
       equivalent  to>=1.1.1 <1.2.0.  So the highest-sorting version that sat-
       isfies~1.1.1is used, which is1.1.2`.

   Caret Dependencies below 1.0.0
       Suppose app has a caret dependency on a version below 1.0.0, for  exam-

         "dependencies": {
           "dep1": "^0.2.0"

       npm  update  will  install  , because there are no other versions which

       If the dependence were on ^0.4.0:

         "dependencies": {
           "dep1": "^0.4.0"

       Then npm update will install , because that is the highest-sorting ver-
       sion that satisfies^0.4.0(>= 0.4.0 <0.5.0`)

   Updating Globally-Installed Packages
       npm  update  -g will apply the update action to each globally installed
       package that is outdated -- that is, has a version  that  is  different
       from latest.

       NOTE: If a package has been upgraded to a version newer than latest, it
       will be downgraded.

       See attributes(7) for descriptions of the following attributes:

       |Availability   | runtime/nodejs/nodejs-8 |
       |Stability      | Pass-thru volatile      |
       o npm help install

       o npm help outdated

       o npm help shrinkwrap

       o npm help 7 registry

       o npm help 5 folders

       o npm help ls

       This    software    was    built    from    source     available     at
       https://github.com/oracle/solaris-userland.    The  original  community
       source   was   downloaded   from     https://github.com/nodejs/node/ar-

       Further information about this software can be found on the open source
       community website at https://github.com/nodejs/node.

                                  August 2018                    NPM-UPDATE(1)