Npm WARN skippingAction Module is inside a symlinked module: not running remove node_modules/anchor/node_modules/validator Npm WARN skippingAction Module is inside a symlinked module: not running remove node_modules/anchor/node_modules/lodash Npm WARN skippingAction Module is inside a symlinked module: not running remove node_modules/anchor/node_modules/geojsonhint

Npm WARN skippingAction Module is inside a symlinked module: not running remove node_modules/align-text/node_modules/kind-of Npm WARN skippingAction Module is inside a symlinked module: not running move node_modules/accepts/node_modules/mime-types

Npm WARN skippingAction Module is inside a symlinked module: not running move node_modules/accepts/node_modules/mime-db If you want some more details, here's a gist demonstrating a series of commands that reproduces our specific scenario.ītw it's worth noting that I tried -global-style and -legacy-bundling to no avail (it was a long shot anyways, but just mentioning it in case it saves anyone some time). Verbose stack TypeError: Cannot set property 'lodash' of undefinedĢ7 verbose stack at /Users/mikermcneil/.nvm/versions/node/v5.4.0/lib/node_modules/npm/lib/install/deps.js:96:36Ģ7 verbose stack at /Users/mikermcneil/.nvm/versions/node/v5.4.0/lib/node_modules/npm/node_modules/dezalgo/dezalgo.js:17:12Ģ7 verbose stack at RawTask.call (/Users/mikermcneil/.nvm/versions/node/v5.4.0/lib/node_modules/npm/node_modules/dezalgo/node_modules/asap/asap.js:40:19)Ģ7 verbose stack at flush (/Users/mikermcneil/.nvm/versions/node/v5.4.0/lib/node_modules/npm/node_modules/dezalgo/node_modules/asap/raw.js:50:29)Ģ7 verbose stack at nextTickCallbackWith0Args (node.js:456:9)Ģ7 verbose stack at process._tickCallback (node.js:385:13) Specifically, the error we're seeing when trying to npm install an unrelated package when there are naughty imposter symlinks in the node_modules/ folder: I'll try to remember to report back here with what we come up with. In the mean time we'll keep searching for a workaround- was going to look into -global-style next, and after that maybe calling npm link and npm link foo programmatically for each dep. It'd be great to be able to work around this in an official NPM way, but I know you guys are busy. it's not that node_modules/ itself is a symlink- rather that the packages are symlinks.įor now we're just sniffing npm -v (if <'v3.0.0' use symlinks, otherwise run npm install manually and display a message). This still works fine- but as soon as our users try to npm install some-other-thing, everything explodes. Thanks! To give you another use case, we ran across this because sails new spits out a new Sails app and creates symlinks to dependencies of the globally installed sails in the new node_modules/ folder (purely to avoid the ~30 sec npm install).

Npm install modules