-
Notifications
You must be signed in to change notification settings - Fork 61
Workaround for deeply nested folders
Marc Harding edited this page Oct 13, 2016
·
1 revision
@patricknelson wrote here
I think ultimately it had more to do with the length of the file path, for which I found a magic bullet for those of us on Windows (everyone here at least).
If the file path is too long (if that's the cause if your issue):
Use the subst command to shorten it, but more importantly, this allows you to easily .... Alias to a path using the \?\ prefix, which is a Windows Unicode workaround that allows for paths up to ~32k in length >(surprisingly, and it works very well). Example command:
subst x: "\?\C:\super\long\path\here" So that then even if you end up with x:\node_modules\inception\node_modules\ ad nauseam, you won't still be capped at the >260 char limit 😄