-
Notifications
You must be signed in to change notification settings - Fork 822
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
Installing gulp-watch on WindowsBash fails on a dependency #697
Comments
It looks like your issue is related to this one: #216 |
Yep. You might be able to put your watcher manually into fallback polling mode like tail -f does automatically if you check the manpage? |
This should now work in Insider builds >= 14942 |
Closing this out since this has been marked fixed for sometime. If the issue persists, please reopen. |
Has there been any updates on how to get gulp-watch to work within Bash on Ubuntu on Windows? I've tried to find any explanation on how to get this to work properly. |
@swagers-sc - what a build are you on? This issue is resolved in Insider builds and will be available when Creators Update ships. |
@benhillis My OS Build is 14393.693 |
@swagers-sc - ok, this will be resolved for you when up install Creators Update (assuming you do not want to opt into the Windows Insider program). |
@benhillis Yeah, I saw that. Looks like there's a tentative release of April for the Creators Update. Thanks again for the speedy response. |
Hello,
I have been trying to utilize the fabulous work you guys have done on WindowsBash to get a build for a product we are developing running on WindowsBash. Our product is a mongo/nodejs/Js/react stack and I have not been successful in getting the backend portion of it running. I'm stuck by gulp watcher failures, which while are not critical, is needed for gulp-sass as we update and modify files.
It should be noted that the problem does not not exist on the same computer running the build we have via CygWin.
When we run gulp using the watcher (which is a file change scanning tool), we get the following error:
I went back to watch how our node modules are being installed and I noticed the following error. After checking on CygWin, I do not see this error.
I can only determine that WindowsBash is preventing file directory access to this module. The error EPERM is related to permissions, but I do not have an idea how to determine exactly what is preventing. I have tried to run gulp as root and I get the same error.
I thought I would submit this as a bug as we do not see this error on Ubuntu platforms where we host our product, on our mac development platforms, no on CygWin. I can only determine that it is related to Windows Bash.
I have the latest Windows Preview build 14393
This morning I used the lxrun /uninstall command to remove and install the latest bash environment
The version of NPM we are running is 3.4.1
The version of Node we are running is 4.3.2
I'm running everything on a Surface Book.
The text was updated successfully, but these errors were encountered: