-
-
Notifications
You must be signed in to change notification settings - Fork 103
lodash's infinitely nested dependency graph collides with Windows path limit of 255 chars, fix tests that fail on windows #23
Conversation
…h limit of 255 chars, fix tests that fail on windows
i'm still unsure about this... |
@jdalton lol :p |
Not sure where the issue is but some part isn't letting Windows know to use its extended-length path. The issue is bound to be more generic than lodash's dep tree. See http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx
|
BTW we have worked to reduce the dep graph of individual modules in the next version bump and we're also deprecating var template = require('lodash/utilities/template'); will be available in v2.5.0. Also the dep graph isn't anything crazy: dedup'ed it's just |
|
I'm suggesting it's an issue in the module that's handling path resolution not something you should be fixing in your test code. |
@jdalton i agree, far from the first time i've seen this though. might already be a ticket in Node on this. |
@jdalton That would be in node core then - AFAIK we are not trying to resolve the path of lodash.template besides requiring it |
Some more digging: https://github.com/joyent/node/blob/master/lib/path.js#L476-L504 shows Node has code to handle long paths in Windows. I just tested this on Windows 7 and didn't run into any issues with Lo-Dash and only tweaked the |
@jdalton https://github.com/joyent/node/search?q=_makeLong&ref=cmdform only seems to be used in fs.exists |
@jdalton thanks for the troubleshooting 👍 |
Yes, the real issue is outside gulp. But requiring a shallower dependency |
What should be done to resolve this? Should the PR be merged or not? |
Closing this as wontfix |
when the dependence |
No description provided.