-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Deprecate #22
Comments
@phated Do you have access on npm? I think we should hold off until we publish 4.0 since it will log deprecation warnings for everyone with 3.x installed |
@contra yeah, I have access. I agree that it shouldn't be deprecated until 4.0 release |
Not going to deprecate this after all. We needed an abstraction for gulp.watch to allow debouncing and queueing. |
H @phated , sorry if this thread is not the right one but couldn't find a better one without opening a new issue I've been using gulp v4 for awhile, at the moment (4.0.2), but every time I install the dependencies on my package.json I get a few warnings of deprecation and upon further investigation I came across that one of them was related to this package which is still using chokidar 2.1.8 (a deprecated version, when the latest version is 3.4.0) The location of chokidar is at in my dependencies: Is this accurate about the version? Can you guys update this or this is going to stay like this? |
We are using chokidar directly in gulp 4, so we should probably deprecate this library.
The text was updated successfully, but these errors were encountered: