Support for filesystem watchers like inotify
Currently there is no support for filesystem watchers like inotify.
Because of this tools like bitbake don't work.
inotify support was added in Win10 Insiders build #14942.
This is the only reason for me not updating into windows 10.
Matthijs Hakfoort commented
This is a blocker for using gulp/grunt file watching, which means we cannot use Bash on Windows for our workflow atm, and we desperately want to!
Michael Stufflebeam commented
tailf, tail -f, and watch all don't work. That sadly breaks our sass and node web development workflow.
Kenan Xin commented
running into issue with nodemon without inotify support
Also running into issue when using Rails 5 and Puma.
This is a **Major** blocker for most web development workflows. Honestly this should be the highest priority for WSL.
Nolan Lawson commented
AFAICT this is the one big thing blocking me from using WSL as my primary command-line. Tools like watch/watchify/etc. are pretty vital to most modern webdev.
+1. Everything is awesome, but this feature is really needed. ;)
Kenneth Chung commented
Yeah... can't really do web dev without this feature. I'm using gulp and watchify.
I can't run any gulp watches at the moment. Which basically breaks our build process. Same goes for EmberJS's `ember server` command. Same issue as Michael Cebrian with the PERM problems. Very annoying since one of the priority features is NodeJS support!
Di Weng commented
I believe it's an essential feature for web developers.
Evan Jacobs commented
I'm working on adding an override to chokidar, so at least scenarios using that will still work on WSL: https://github.com/paulmillr/chokidar/pull/497
Dave Rupert commented
This is a blocking issue for using lots of Node and Ruby workflows.
Michael Cebrian commented
All of the node.js watch functions that I've tried fail on EPERM. I've ensured that all files and directories that it's trying to access have the proper ownership group and user. I even tried running watch tasks as the root user, and I receive the same eperm issue. I've also made sure that all of the files are listed inside the linux subsystem, and that I'm not trying to watch files mounted to /mnt/c/