-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
Thanks for the contribution! :) It is failing AppVeyor CI Windows tests because |
We do this already. https://github.com/paulmillr/chokidar/blob/master/lib/fsevents-handler.js In fact, it was failing before this commit. |
Hmm I think I saw some packages that use chokidar and are tested by appveyor. Need to find these |
Here's a quick example https://github.com/AppGyver/steroids/blob/master/package.json Chokidar is tested by it too :) https://github.com/paulmillr/chokidar/blob/master/appveyor.yml |
Hmm, then I think we should remove
Nope, the current master is not failing: https://ci.appveyor.com/project/sass/node-sass/build/889. |
Ah, i've meant the tests are failing on my machine. I will provide logs later (were doing npm test) |
Ping 🔔 |
@am11 what's required from me? That doesn't seem like Chokidar error. Just tested it locally — all tests pass. |
@@ -20,6 +20,5 @@ install: | |||
- node --version | |||
- npm --version | |||
- git submodule update --init --recursive | |||
- ps: npm install --msvs_version=2013 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just remove ps:
prefix, not the entire statement.
- npm install --msvs_version=2013
LGTM! @xzyfer, if this has been triaged with CI tests, then it can probably be considered for vNext as a non-breaking infrastructure change. Thoughts? |
@xzyfer ping. |
Curious on that status of this ticket since when installing node-sass now you get a warning that it uses a deprecated version of lodash. The reason is that node-sass is using an old version of gaze (0.5.* instead of 0.6.*). Maybe you could try the new version until you change to Chokidar? |
We've been waiting to see if Chokidar would gain traction. As for gaze, the |
@xzyfer curious what do you actually mean by "traction".
|
@paulmillr I understand what you're saying. Chokidar has clearly gained traction since this PR opened. To be more explicit there are a couple reasons we have not moved forward on this:
At the moment, as far as I know, neither grunt or gulp has switch to chokidar in their stable releases. Once gulp 4 is stable a large portion of our user base will be using chokidar and the migration will be a much smaller support risk. I hope you understand. We're a very small team and we hugely appreciate your contribution. |
We also had to make a one step back - all tests for the CLI watcher have been removed, because they were poorly written. We will need those tests back. |
Any update on this? |
6c128d9
to
1e4bba8
Compare
in the meantime checkout https://github.com/michaelwayman/node-sass-chokidar
|
I think this has been taken care of with 80fc103 |
Correct |
😸 |
Hey, what's the status on this? It seems like |
Ooh, good to hear! Thanks! |
It looks like this didn't land in the final v5 release. What happened? |
Correctly bubble keyfrome directives
Closes gh-636. Tests fail because of something else.
To summarize: chokidar is very stable, doesn't have 52 open issues and is much faster on OSX, with less CPU usage because of
fsevents
.