The dependency chain is too deep for windows

[Pomax]

If I include brackets as a git submodule in my own project, its node_modules dependency chain is so incredibly deep it breaks windows' path length restrictions while cloning --recursive. Would it be possible to optimize this so that it's not node_modules in node_modules in node_modules in node_modules, but npm deduped all to the same depth?

[thany]

That's more likely a bug in npm, since Windows' maximum path length is actually 32767 (minus a few) characters. It's unlikely that anything will ever get that far.

[Pomax]

you clearly never looked at the previous Lodash version's requirement chain. It was truly incredible =)

That said, there are definitely things that can be done to fix it (dependency consolidation at higher levels, checking which dependencies at the major offenders, at which depth, and getting those projects to use optionalDependencies so that the deps only get installed "if not already found in a higher level", etc)