-
Notifications
You must be signed in to change notification settings - Fork 66
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
remove fsevents #130
remove fsevents #130
Conversation
2bfc91b
to
56ebd34
Compare
Spoke with @amasad in person yesterday this can be safely removed, as the original use-case (from jest) has taken a different approach. If users are having FS watching issues, OSX's filewatching is pretty sad, we strongly recommend they utilize watchman. |
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.
👏
released as v4.0.0 🎉 |
Is there a reason |
Seems like an oversight, mind sending a PR? |
@wtgtybhertgeghgtwtg thanks, I released your fix as v4.0.1 🎉 |
Great--thanks @stefanpenner et al |
Question, what is that approach? Jest currently uses the |
ping @stefanpenner. |
Any chance of reverting this? We have to vendor the previous solution in Jest (due to jestjs/jest#8088, jestjs/jest#8258). I don't know what the motivation for removing it was, but v2 of |
I’ll take a look once I return of vacation. If you don’t hear from me by next week, it may have gotten dropped. Feel free to reping |
@stefanpenner ping 😀 |
Summary: sane@2 added fsevents support. sane@3 bumped the minimum node version to 6.0, same as ours. sane@4 removed fsevents support, but that seems to be controversial, so excluding it for now: amasad/sane#130 Reviewed By: gabelevi Differential Revision: D17425813 fbshipit-source-id: 426aee1710cd84a5bf27ddbfc8c5977b33e053fd
@stefanpenner any news here? |
@stefanpenner 2020 ping 🎆 |
No description provided.