-
-
Notifications
You must be signed in to change notification settings - Fork 505
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
Potentially switch from chokidar to @parcel/watcher or turbowatch #3149
Comments
I’m assuming this should be moved to |
Ah okay, makes sense! I thought that was the main watcher in general. Thanks for the correction. |
Whoa, just saw https://github.com/parcel-bundler/watcher?tab=readme-ov-file#querying which would be a pretty big win for incremental builds. |
does @parcel/watcher support polling though? parcel-bundler/parcel#564 |
Good callout. I have access to WSL for testing, if/when I tackle this one I’ll make sure to test appropriately. |
https://github.com/parcel-bundler/watcher seems like a much better alternative to Choikdar. It's already used by projects like Tailwind, Nx, Nuxt, VSCode, etc (https://github.com/parcel-bundler/watcher#who-is-using-this). Vite considered switching to it but it happened to be too large of a milestone before Vite 5. On that note, https://github.com/gajus/turbowatch also seems interesting. 👀
The text was updated successfully, but these errors were encountered: