![]() 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).
0 Comments
Leave a Reply. |