-
Notifications
You must be signed in to change notification settings - Fork 47
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
Windows 10 non existent folders causes onchange to fail #50
Comments
Have you tried single quotes? I don't use Window personally, but I know there's some oddities. On another note, I'd just recommend combining them in a glob pattern: |
I did try single quotes, that doesn't work at all. There is documentation about the quotes in the
I am not sure if I can combine them in a glob pattern like you recommend as my actual code looks more like this: Noting that I have files that match this pattern |
You can do |
Oh, I misread the issue too - this is specifically when starting the command and the directory doesn't exist? What's the error? This looks like something we should log in |
Does this sound related: paulmillr/chokidar#346? |
It's definitely that issue cheers mate. |
Ok, so you can do |
I did try For instance I made changes in |
I'm going to close this issue as it's related to chokidar. |
When running onchange in windows 10 I can get the function to work when I have the
app
directory:onchange \"app/**/*.js\" -- npm test
However it doesn't work when I have the
app
directory but not thetest
directory:onchange \"app/**/*.js\" \"test/**/*.js\" -- npm test
There seems to be an issue with non existent folders when using onchange on Windows 10.
The text was updated successfully, but these errors were encountered: