npm 3.0 flattens hierarchy, causes npm-shrinkwrap "extraneous" errors

[peacechen]

One of npm 3.0's improvements is that it flattens the node_modules dependency hierarchy. This causes npm-shrinkwrap to fail with "extraneous" errors. It looks like npm-shrinkwrap is getting confused because subdependencies are being pulled up into the root node_modules directory.

Recreate by installing npm 3.0. Delete existing node_modules dir and run npm install. I also ran npm dedupe, though that may not be necessary. Then run npm-shrinkwrap --dev.

[clark800]

This is a blocker even for users who are not using npm 3.0. The fsevents package is a sub-...-sub-dependency of my project (via webpack) and it was built with npm 3.0, so I can't use npm-shrinkwrap on my project even though I'm using npm 2.11.3.

[geertweening]

+1 also seeing this issue

[jfurrow]

+:100:

[kigorw]

+:100:

[Raynos]

This tool is not supported with npm3.0. I'm sorry.

I suspect that the majority of problems that this tool fixes have been resolved in npm3.0

Try just using npm shrinkwrap instead of npm-shrinkwrap with npm@3

[IanVS]

As more and more users are switching to npm@3, it might be worth adding a note to the readme that this tool is not intended to be used with npm > 2.

[manonthemoon42]

Any updates on that :( ?