Conversation
8706d4e to
3a77511
Compare
cec4d0c to
8bd789f
Compare
21a8589 to
873087c
Compare
a6ec4bc to
53846f1
Compare
f2fa4d2 to
922d758
Compare
c71632c to
e2278bc
Compare
7800840 to
fec7c37
Compare
|
Closing this as its tasks have been split into issues and we won't be landing it via pull request anyway. |
|
Is there a good way to track the progress of this? |
|
I'm also looking for the progress. I'm on Windows and running into the "path too long" problems of nested node_module dependencies. My understanding was that dedup in its current form does not solve this problem and that "multi-stage-install" was going to solve this. Where are we at now with this? |
|
Looks like it's now on this branch: https://github.com/npm/npm/commits/multi-stage |
|
@Fishrock123 @prettycode Yeah, sorry for not responding earlier. There's a |
|
Any updates on when this work will make it into master / an official release? |
--saveis used.This will ultimately fix multi-stage install #5919 et al.
Builds now occur in node_modules/.staging and modules are only moved to their respective locations at the very end of the process.
See also the design doc on install semantics.