docs(reconciler): document removal of flushSync for custom renderers #35472
+15
−0
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.
This PR documents the removal of flushSync from the react-reconciler public API and clarifies the supported replacement APIs for custom renderers.
Summary
flushSync was previously exposed on the react-reconciler export and was removed in v0.31+ as part of PR #28500. After this change, accessing flushSync from a custom reconciler returns undefined with no documentation or migration guidance.
Custom renderers that followed the earlier documented pattern:
silently broke after upgrading.
This PR documents the intended replacement APIs for synchronous work in custom renderers:
updateContainerSync
flushSyncWork
The goal is to make this breaking change explicit and provide clear guidance for renderer authors.
How did you test this change?