App Router: `loading.js` fallback not streamed in initial HTML
#1.528 geöffnet am 22. Mai 2026
Repository-Metriken
- Stars
- (8.120 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 1T 1h) (462 gemergte PRs in 30 T)
Beschreibung
This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext
mainvs Next.jsv16.2.6, 2026-05-22).
Problem
Pages that have a slow layout.js/page.js should stream the loading.js fallback content in the initial HTML response. vinext serves an empty body for these tests, indicating the Suspense boundary does not flush the loading fallback before the slow content resolves.
Expected: "Loading..." Received: ""
Expected: "Loading layout..." Received: ""
Estimated Impact
~2 test failures across the deploy suite.
Affected Test Suites
test/e2e/app-dir/app/index.test.ts(2 failures)
Recommendation
-
Reproduce first in vinext's own test suite. Add a slow async server component with an adjacent
loading.tsx. Assert the initial response body contains the loading fallback text. -
Flush the suspense boundary fallback eagerly. During streaming SSR, emit each Suspense fallback as soon as the boundary suspends, then patch in the resolved content as it completes. Match Next.js's streaming output shape.
Part of #1328.