-
Notifications
You must be signed in to change notification settings - Fork 525
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
Paket exe can't handle paths that are longer than 260 characters. #949
Comments
Detailed stack trace:
|
also reported in https://twitter.com/chrismckee/status/626756973283950592 |
we could try adding support for the |
+1 When it does find all refs is it scanning all the folders? Just wondering as I have a 'master' folder in my repo which isnt part of the solution, in there is some frontend crap for gulp that handles live reload etc; It's only the npm folder in here that exceeds the win limit (mostly caused by lodash dependencies). But I wouldn't expect Paket to be looking at anything thats not in SLN/CSProj |
could you please check if 1.22.0-alpha005 fixes it? |
it does fix the issue for me. Thanks for the quick turnaround, @forki. |
ok cool. will release a proper version. |
Yup that wins :) Thanks |
can you also push an update of Paket.VisualStudio to contain this fix? It's a bit of heartburn for us without it. |
Already done
|
Hi, I still get the issue especially with the new core libs which have really long name like |
The PathTooLong Exception is still happening What broke it again? |
Between version 1.19.6 and 1.19.7 Paket became unable to handle paths longer than 260 characters. any paket operation, whether via command line or VS integration, blows up with a PathTooLongException now in a solution we have that is a web app, and so has very long nested node_modules directories.
The text was updated successfully, but these errors were encountered: