RFC: Unified cancellation via AbortSignal across React async APIs #271
+847
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
React now spans client and server with transitions, Suspense/use, and server actions, but there is no unified way to cancel stale async work. This RFC proposes an opt-in, web-standard cancellation model using
AbortSignalthat flows consistently through these APIs, withsignal.reasonfor diagnostics and full backwards compatibility.The goal is to stop irrelevant work predictably, reduce wasted I/O and compute, and align React with platform semantics. The proposal includes complete examples, signal composition helpers, and integration patterns for library and framework authors.
This RFC is ready for review. I welcome design feedback and real-world use cases from the React community.