-
Notifications
You must be signed in to change notification settings - Fork 47.2k
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
suggestion: Suspense support delay #24238
Comments
Can you be a bit more specific about what you're using Suspense for? Is it code splitting, data fetching, or something else? There are different solutions to this depending on what you're hitting. |
Are you using the legacy import { createRoot } from "react-dom/client";
const root = createRoot(domElement);
root.render(<YourApp />); |
There seems to be some regression on Suspense fallback commit throttling? reproduced with below demo in React 18-alpha version, throttled codesandbox link I also pulled a DRAFT pr #24253, but not confident enough for review yet.. |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you! |
React version:
Steps To Reproduce
Link to code example:
The current behavior
The expected behavior
can Suspense support delay?
Everytime when render page, the fallback will first show, no matter components get fast
The text was updated successfully, but these errors were encountered: