Skip to content
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

File path length #630

Closed
robertmain opened this issue Aug 15, 2014 · 11 comments
Closed

File path length #630

robertmain opened this issue Aug 15, 2014 · 11 comments

Comments

@robertmain
Copy link

When working with gulp on a Windows machine, the setup of gulp results in a file path that is too long for Windows to be able to delete. This makes it difficult to delete any folder containing gulp.

Long directory tee

Do you want to delete

Clicking "Yes" then results in an error message saying the file path is too long
File path too long

Obviously on a Linux machine or a Mac, this isn't an issue, but I'm part of a team that are considering using gulp for work and are therefore using Windows machines.

@yocontra
Copy link
Member

Update, this has been fixed

@robertmain
Copy link
Author

Do you happen to know which commit fixes this?

@yocontra
Copy link
Member

@robertmain yocontra/glob2base@965c6cc

Run npm ls glob2base and if it's less than 0.0.11 you need to make sure you update or reinstall so you get the latest version.

@u01jmg3
Copy link

u01jmg3 commented Aug 15, 2014

I am facing the same problem and I've just updated gulp (cleaning npm-cache first) but glob2base is still being grabbed at v0.0.9. I can see on www.npmjs.org the latest version is v0.0.11 - do I need to manually change a package.json somewhere?

@yocontra
Copy link
Member

Found the issue - glob-stream was never updated to include the new glob2base. Fixing it now

@yocontra
Copy link
Member

If you npm update now you should get glob-stream 3.1.15 which has the new glob2base dep

@u01jmg3
Copy link

u01jmg3 commented Aug 16, 2014

All good on my end now for gulp. However, I am seeing the same file path length issue on Windows with four gulp plugins I use:

  1. bower (will delete but complains of length)
  2. gulp-imagemin (cannot delete without shortening path)
  3. gulp-jscs (cannot delete without shortening path)
  4. pageres (will delete but complains of length)

The dialog that appears for gulp-jscs mentions lodash.noop. Should I report to each individual repo?

@phated
Copy link
Member

phated commented Aug 16, 2014

We have no control over plugins. Please report on individual projects.

@terinjokes
Copy link
Contributor

Also note:

  1. The next version of lodash attempts to sidestep the path issue on Windows.
  2. The npm team is working hard on resolving the path issue on their end, so hopefully this won't be an issue.

@u01jmg3
Copy link

u01jmg3 commented Aug 17, 2014

Thanks @terinjokes - that's positive news

@jdalton
Copy link

jdalton commented Feb 12, 2015

Just a heads up. lodash v3 has significantly reduced the dep graphs of its modularized packages:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants