enhance: Do not Suspense fallback warning in NextJS server-side #3718
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.
Motivation
The
SSRDataProvidercomponent was usingBackupLoadingas its Suspense fallback, which displays an "Uncaught Suspense" warning in development mode. This warning is misleading during Next.js server-side rendering because:Solution
Replace the
BackupLoadingfallback withnullinSSRDataProvider. This silences the confusing warning while maintaining the same functional behavior - the outer Suspense boundary still catches suspense during SSR, just without rendering a misleading development message.Note
Removes the misleading "Uncaught Suspense" dev warning during Next.js SSR by changing the Suspense fallback in
SSRDataProvider.SSRDataProvider, replaceBackupLoadingwithnullasUniversalSuspensefallback to avoid the warning during expected SSR suspense@data-client/reactWritten by Cursor Bugbot for commit d93d145. This will update automatically on new commits. Configure here.