If you are using a relatively new version of npm (I used version 2.14.2), you can damage the version number in package.json and npm update dep_1 . Otherwise, how can npm know that something needs to be updated?
Note. . This will only work if the version is higher than previously installed. You will have to clear the cache before resetting this behavior.
However, you can force (and lazily) update local modules by simply running npm install again. eg.
npm install dep_1
It should be fast, since it is located on your local computer, and you do not need to play with version numbers.
See the discussion of this issue on the official npm repository page for more details: https://github.com/npm/npm/issues/7426
chriskelly
source share