2.1.2 does not react to file changes anymore about eslint-watch

[rizowski]

@simonvizzini If you do esw -v what version does it say? That prints out the eslint version. I don't think eslint is the cause but you never know lol.

[rizowski]

Also can you try saving multiple times and let me know if it picks up the file changes? I have been seeing it not pick up the first save, but after that it continues to lint fine.

It also seems to only happen when passing in multiple arguments. Passing in a single directory works as intended.

[simonvizzini]

esw -v outputs "1.5.1" (just saw that eslint 1.6.0 is out, so I'll give it a try). I tried saving multiple files multiple times, but still no luck. I also just tried to watch just one folder but that doesn't work for me either.

I guess this could be a problem in the chokidar module instead. Current version is 1.2.0 (released a week ago) and this version has been installed as a dependency of eslint-watch, so maybe something is broken there. I will try to manually setup a file watcher with chokidar and see if it detects any changes. Unfortunately I have to leave now, but will try this on Monday and report back. In the meantime: have a nice weekend! =)

[rizowski]

Have you tried using 1.2.5 or 1.2.6 for eslint-watch? I am trying to figure out when this was introduced.

Neither really do much. But It all seems to revolve around that keylistener I put in.

[Cordazar]

My findings suggest that something in watcher.js messes up the input glob.

Because if I run esw . -w or esw ./ -w I will get proper linting but not any watcher that works. And if I just run esw -w and let it use the default ./ path the watcher works as it should.

I don't have time right now to debug this properly but hopefully this helps narrow down the scope. I also took a quick look at chokidar 1.2.0 but it works as it should with . or ./ .

[rizowski]

@simonvizzini @Cordazar Sorry for the delay in getting this fixed. I have been busy with work and life. I will make an effort this week in getting this resolved.

[rizowski]

@simonvizzini @Cordazar I have a fix out there pending a review. It seems like all the magic that was put into the watcher was unneeded bloat. If you wouldn't mind verifying that the fix works for you, that would be awesome and would help a lot. It's on the branch watch-fix. Sorry again for the delay.

[rizowski]

I have released what I had. It should be on version 2.1.3. I had someone test it out and they couldn't reproduce it on their machine.

[simonvizzini]

Hey @rizowski, so sorry for the late response yet again. As I was getting closer to a deadline, my workload started to increase exponentially :-) But now the dust has almost settled, and I definitely want to keep my node package dependencies up-to-date. I'll update all my node modules in the next couple of days and let you know if everything is okay. Thanks a lot so far and I promise to give feedback asap

[simonvizzini]

Hey again! So I finally updated my npm packages and I can confirm that the file watcher now works fine on Windows. Thanks!

[rizowski]

@simonvizzini Good to hear! 😄 Thanks for the update.