4 ms·
> npm and 260 char limit for path on Windows was driving me nuts. If you can upgrade, node 5/npm 3 fixed the by flattening out the node_modules folder as much
by madeofpalk 11y ago
> npm and 260 char limit for path on Windows was driving me nuts.
If you can upgrade, node 5/npm 3 fixed the by flattening out the node_modules folder as much as possible.
- toupeira 11y ago"As much as possible" would be doing node_modules/$PACKAGE-$VERSION for all packages (like e.g. Rubygems does). But instead they're doing node_modules/$PACKAGE and still nesting conflicting dependencies, so it's entirely possible to still run into the same issue.