cloudflare/vinext

App Router: `reactMaxHeadersLength` config not respected

Fechada

#1.552 aberto em 22 de mai. de 2026

 (3 comentários) (0 reação) (0 responsável)TypeScript (383 forks)github user discovery
adapter-api-e2ehelp wanted

Métricas do repositório

Stars
 (8.624 estrelas)
Métricas de merge de PR
 (Mesclagem média 1d 1h) (462 fundiu PRs em 30d)

Description

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.

Guia do colaborador