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

Closed
petermorlion opened this Issue Feb 10, 2016 · 7 comments

Comments

Projects
None yet
6 participants
@petermorlion
Contributor

petermorlion commented Feb 10, 2016

Hi, I'm wondering if anyone else has experienced a PathTooLongException when generating docs, and if there is a workaround.

@simonmurdock

This comment has been minimized.

Show comment
Hide comment
@simonmurdock

simonmurdock Feb 10, 2016

I hit this issue all the time with all my tools. I just have to work out of C:\dev\branch\

simonmurdock commented Feb 10, 2016

I hit this issue all the time with all my tools. I just have to work out of C:\dev\branch\

@petermorlion

This comment has been minimized.

Show comment
Hide comment
@petermorlion

petermorlion Feb 10, 2016

Contributor

Thanks, I'll give that a try.

Contributor

petermorlion commented Feb 10, 2016

Thanks, I'll give that a try.

@chenkennt

This comment has been minimized.

Show comment
Hide comment
@chenkennt

chenkennt Feb 29, 2016

Contributor

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.

Contributor

chenkennt commented Feb 29, 2016

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.

@gitting

This comment has been minimized.

Show comment
Hide comment
@gitting

gitting Mar 8, 2016

This just happened to me after updating some package with npm.

I found flatten-packages useful to fix this. Just install it as they say, then run in the directory where your offending project.json is.

gitting commented Mar 8, 2016

This just happened to me after updating some package with npm.

I found flatten-packages useful to fix this. Just install it as they say, then run in the directory where your offending project.json is.

@superzadeh

This comment has been minimized.

Show comment
Hide comment
@superzadeh

superzadeh May 2, 2016

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.

superzadeh commented May 2, 2016

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.

@superyyrrzz

This comment has been minimized.

Show comment
Hide comment
@superyyrrzz

superyyrrzz May 13, 2016

Collaborator

The exclude field in docfx.json can be used to filter out the unwanted folder since DocFX 1.9, e.g. "exclude": ["**/node_modules/", "**/bower_components/"]. Remember to exclude them in both metadata and build step if needed.

Collaborator

superyyrrzz commented May 13, 2016

The exclude field in docfx.json can be used to filter out the unwanted folder since DocFX 1.9, e.g. "exclude": ["**/node_modules/", "**/bower_components/"]. Remember to exclude them in both metadata and build step if needed.

@superzadeh

This comment has been minimized.

Show comment
Hide comment
@superzadeh

superzadeh May 13, 2016

The problem is that some of these long paths are wanted (they're not node/jspm modules, they're actual code).

superzadeh commented May 13, 2016

The problem is that some of these long paths are wanted (they're not node/jspm modules, they're actual code).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment