-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
breaking: avoid flushing queued updates on mount/hydrate #12587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: 2901e6e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
With this change, is there still a difference between |
Co-authored-by: Rich Harris <[email protected]>
Doesn't it have some usage still for avoiding the microtask being created? In any case, we can defer that to an issue or another PR. I don't think it needs to be attached to this change. |
)" This reverts commit 20b8797.
I have a hunch that this might fix #12477.
Ultimately though,
mount
andhydrate
shouldn't be considered synchronous. It prevents us from doing asynchronous things in the future, plus it slightly negatively impacts performance.