App Router: `reactMaxHeadersLength` config not respected
#1,552 opened on 2026/05/22
Repository metrics
- Stars
- (8,563 個のスター)
- PR merge metrics
- (平均マージ 1d 1h) (30d で 462 merged PRs)
説明
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
The reactMaxHeadersLength config option (which controls how much React inlines into HTTP headers like Link preload hints) is not honored — the expected header that should be set when this option is configured is always null.
With `reactMaxHeadersLength` configured, expected Link preload header set; received null
Estimated Impact
~3 test failures across the deploy suite.
Affected Test Suites
test/e2e/app-dir/react-max-headers-length/react-max-headers-length.test.ts(3 failures)
Recommendation
-
Reproduce first in vinext's own test suite. Configure
reactMaxHeadersLength: 16000and assert the expected Link header is emitted. -
Forward the option into the React renderer. Pass
reactMaxHeadersLengthtorenderToReadableStream/renderToPipeableStreamso React inlines preload hints into headers up to the limit.
Part of #1328.