-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Unable to run gulp #2435
Comments
@blindbox are you able to run any other program installed using |
Nope. Here's one with maildev.
My nodejs install is in F drive, and so is my yarn install. I was thinking it might be related to nodejs being installed in a different drive. So, with both NodeJS and Yarn installed to drive C, here's what I get: Using command prompt
Using git bash (it works!) $ maildev --version
0.14.0
I think the files generated by yarn can be quite interesting. Here's one when I installed yarn and nodejs on drive C (there's two files): "$basedir/../../Users/user/AppData/Local/Yarn/config/global/node_modules/.bin/maildev.cmd" "$@"
exit $? File @"%~dp0\..\..\Users\user\AppData\Local\Yarn\config\global\node_modules\.bin\maildev.cmd" %* Here are the same two files, generated when nodejs and yarn is installed in drive F. "$basedir/C:/Users/user/AppData/Local/Yarn/config/global/node_modules/.bin/maildev.cmd" "$@"
exit $? File @"%~dp0\C:\Users\user\AppData\Local\Yarn\config\global\node_modules\.bin\maildev.cmd" %* Also to note, running maildev.cmd.cmd instead of maildev makes maildev work. |
I just noticed that this might be a duplicate of #2224 (didn't think of search for the windows tag) |
@modulexcite noticed #2224 (comment) that issue is fixed. |
It works. Awesome, this has been a gamebreaker preventing me from using yarn completely. Just in case, if anyone tried reinstalling and it still doesnt work, make sure you delete all traces of *.cmd and *.cmd.cmd files that yarn generated from previous installs, and try again. |
Do you want to request a feature or report a bug?
A bug. Issue #927 might be related.
What is the current behavior?
Installing gulp-cli using
yarn global add gulp-cli
leads to the following error when runninggulp
Alternatively, if ran through a git bash, I'll instead get this error:
If the current behavior is a bug, please provide the steps to reproduce.
yarn global add gulp-cli
gulp
through Git Bash or cmd.exeWhat is the expected behavior?
Gulp should run without any errors.
Please mention your node.js, yarn and operating system version.
node: v6.9.4
yarn: 0.18.1
OS: Windows 7 64-bit Ultimate.
The text was updated successfully, but these errors were encountered: