-
Notifications
You must be signed in to change notification settings - Fork 865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PathTooLongException #156
Comments
I hit this issue all the time with all my tools. I just have to work out of C:\dev\branch\ |
Thanks, I'll give that a try. |
Hi @petermorlion , PathTooLong is a restriction in Windows (maximum 260 characters). If you met this issue, please try to reduce the length of your working directory. We'll also improve the error message. |
This just happened to me after updating some package with I found flatten-packages useful to fix this. Just install it as they say, then run in the directory where your offending |
I also face this problem, one possible workaround would be to use the BCL team's LongPath library. Would that be an acceptable workaround? If so, I could start working on a PR for this. |
The |
The problem is that some of these long paths are wanted (they're not node/jspm modules, they're actual code). |
Hi, I'm wondering if anyone else has experienced a
PathTooLongException
when generating docs, and if there is a workaround.The text was updated successfully, but these errors were encountered: