Now, you can control when to update a dependency to a new version. The command npm shrinkwrap produces a npm-shrinkwrap.json file that locks down your dependencies' versions. Almost, because you will need to be aware of packages with install scripts or node-gyp dependencies which are typically platform-specific. just copy itĪ straight forward method to prevent issues on production would be to use the almost fail-safe solution of deploying your code with the node_modules folder. You will need to upgrade those to dependencies. If you have dependencies or projects using peerDependencies, they will be ignored by npm3.

The only way to reliably get the same dependency tree is by removing the node_modules folder and proceed to install all the dependencies again. npm3 will attempt to flatten the dependency tree and the dependency resolution depends on install order. Npm3 resolves dependencies differently than npm2. npm2 vs npm3Ī great source of confusion and problems comes from upgrading npm to version 3. Such tales help keep life interesting but for those that want to keep their sanity I'll go over some of these npm quirks and features you should be aware of and take some time to look into. There's an interesting tale from Tictail (the perfect npm storm) on such an event. If you are using Node.js, you will have used it and you will be familiar with it, but since it works so well you don't take much thought into it until it doesn't.

Npm config set cache