cloudflare/vinext

App Router: `reactMaxHeadersLength` config not respected

已關閉

#1,552 建立於 2026年5月22日

 (3 則留言) (0 個反應) (0 位負責人)TypeScript (385 個分叉)github user discovery
adapter-api-e2ehelp wanted

倉庫指標

星標
 (8,633 顆星)
PR 合併指標
 (平均合併 1天 1小時) (30 天內合併 462 個 PR)

描述

This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext main vs Next.js v16.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

  1. Reproduce first in vinext's own test suite. Configure reactMaxHeadersLength: 16000 and assert the expected Link header is emitted.

  2. Forward the option into the React renderer. Pass reactMaxHeadersLength to renderToReadableStream/renderToPipeableStream so React inlines preload hints into headers up to the limit.


Part of #1328.

貢獻者指南