rapidrest / react / 36204354214

100%

push

github

Fix the dev server crashing with "EPERM: operation not permitted, watch" on Windows, and staying down until the next file change, whenever a client rebuild replaced the Vite manifest, because the fs.watch on it emitted an 'error' event that nothing listened for and an unhandled 'error' event is fatal in Node, while the try/catch around fs.watch only covered it throwing synchronously Have a watcher 'error', or a 'rename' from a watcher that keeps watching the deleted file, end that watch and look for the replacement manifest for up to five seconds, then watch it and reload the browsers, which also stops live reload silently ending after the first rebuild Add tests with a realistic fake watcher for the error, the rename, repeated rebuilds, waiting for the manifest to come back and giving up, verify against a real fs.watch that the original code produces the EPERM and the fix does not, and document the fix in the changelog and release notes

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

439 of 439 branches covered (100.0%)

Branch coverage included in aggregate %.

24 of 24 new or added lines in 1 file covered. (100.0%)

668 of 668 relevant lines covered (100.0%)

219.07 hits per line