cloudflare/vinext

App Router: `reactMaxHeadersLength` config not respected

已关闭

#1,552 创建于 2026年5月22日

 (3 条评论) (0 个反应) (0 位负责人)TypeScript (383 个派生)github user discovery
adapter-api-e2ehelp wanted

仓库指标

星标
 (8,624 个星标)
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.

贡献者指南