Matt Cowley

👋 I'm also running into this, but specifically only after updating to `[email protected]`. If I roll back to `[email protected]`, it does not crash. Looking at https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/compare/v9.0.3...v9.1.0 leads me to suspect...

I don't have a PR to fix the issue -- I'm not sure what the best fix would be, perhaps using graceful-fs, but I leave that to the maintainers.

Fwiw, there are two `watchOptions` Webpack settings that also seem to be a workaround for this as also suggested in the upstream chokidar issue (though I do not consider them...

👋 @Schniz checking in on this one -- this is the install path we're recommending by default on nodejs.org for Windows users now, and folks are getting stuck due to...

This is an open-source project, if the config is invalid you are welcome to open a PR to fix it. If the config is valid, this is likely impacted by...

Hi. I no longer work at DigitalOcean. Also, what you're reporting seems in no way related to this issue. Please open a new issue in GitHub when reporting something unrelated...

(speaking for myself) the editor we use on Community (built with Slate) is something that I've wanted to open-source for a while now since I built it internally. I believe...

Major +1 here, the frequent releases and website updates cause a full cache purge in Cloudflare every single time, putting a massive load on the origin that it is currently...

I think perhaps the wording here, regarding freezing of releases, was intended to also capture the release of nightly/canary builds, as those also cause cache purges. While I agree I...

+1, the website is no longer served out of NGINX and releases are now served from R2 afaik, so I think this is no longer a problem.