-
Notifications
You must be signed in to change notification settings - Fork 3k
[npm5]npm i with package moved lead to an incorrect package.json in node_modules, which cause Cannot find module
#17267
Comments
Not sure whether it's the reason for #16947 |
UPDATE 20170630
And found the same issue in Log of npm i
Log of npm dedupe
But this one is not extra the same as the first one. This one doesn't need twice |
Do some debug, and found the reason is https://github.com/npm/npm/blob/v5.0.3/lib/install/action/move.js#L29 -- Still not sure why twice install with the same pkg&ver is needed to get the final result, maybe also related to |
Cannot find module
Unable to reproducted in |
I'm opening this issue because:
What's going wrong?
main
is lost after move, which makes it FAILED to be require(). "> " is inserted todescription
,_location
is not changed.(Major)https://gist.github.com/yyjdelete/6c3200abc8046852329dbea0003f0e26
How can the CLI team reproduce the problem?
supporting information:
npm -v
prints:5.0.3
/5.0.3-canary.12
(npmc)node -v
prints:v8.1.1
npm config get registry
prints:http://registry.npm.taobao.org/
Windows
The text was updated successfully, but these errors were encountered: