11ty/eleventy

Potentially switch from chokidar to @parcel/watcher or turbowatch

uncenter opened this issue · 5 comments

uncenter commented

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. 👀

zachleat commented

I’m assuming this should be moved to 11ty/eleventy—the chokidar usage here is strictly for the standalone dev-server CLI. If we change it upstream in Eleventy core, we can talk about applying it to the dev server CLI too!

uncenter commented

Ah okay, makes sense! I thought that was the main watcher in general. Thanks for the correction.

zachleat commented

Whoa, just saw https://github.com/parcel-bundler/watcher?tab=readme-ov-file#querying which would be a pretty big win for incremental builds.

  • 🚀1
  • 👀1
murtuzaalisurti commented

does @parcel/watcher support polling though? parcel-bundler/parcel#564

  • 👀1
zachleat commented

Good callout. I have access to WSL for testing, if/when I tackle this one I’ll make sure to test appropriately.

  • 👍1