request.signal is never fired in dev server - Githubissues

remix-run / remix

Build Better Websites. Create modern, resilient user experiences with web fundamentals.

https://remix.run

MIT License

28.15k stars 2.36k forks source link

request.signal is never fired in dev server #9438

Open DanielBaulig opened 2 weeks ago

DanielBaulig commented 2 weeks ago

Reproduction

https://stackblitz.com/edit/remix-run-remix-jkyczz?file=app%2Froutes%2Fstream.tsx

Based on discussion: https://github.com/remix-run/remix/discussions/8461

The effects of the bug are twofold:

Actual abort signal behavior cannot be tested and verified using the dev server.
The dev server might leak resources that should have been freed when the request was cancelled.

Not that the bug only applies to the dev server. Using the express server the request abort signal is fired correctly.

System Info

See Stackblitz

Used Package Manager

npm

Expected Behavior

Dev server should print 'Received Abort!' when the response gets cancelled a second in.

Actual Behavior

Silence.