You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following is parsed automatically by the Next.js repo e2e test report generator.
test: test/e2e/app-dir/react-max-headers-length/react-max-headers-length.test.ts
reason: Undocumented next@15-canary reactMaxHeadersLength config option is not respected; cannot debug due to React 19 RC being closed source
The text was updated successfully, but these errors were encountered:
next@v15.0.0-canary.99 added a new
reactMaxHeadersLength
option tonext.config.js
.It was introduced in this PR: vercel/next.js#67715. This gets passed to react-dom's
renderToReadableStream
here: https://github.com/vercel/next.js/blob/4837a67fb9bc7199e48cd8bd2cc42659b17dfacc/packages/next/src/server/app-render/app-render.tsx#L1490. This was presumably added in a react 19 RC version, but react 19 is being developed in secret so we can't see the source 🤷🏼♂️.One theory is that this functionality doesn't play nicely with our use of a
TransformStream
:next-runtime/src/run/handlers/server.ts
Line 135 in f10d661
Data
The following is parsed automatically by the Next.js repo e2e test report generator.
test: test/e2e/app-dir/react-max-headers-length/react-max-headers-length.test.ts
reason: Undocumented next@15-canary reactMaxHeadersLength config option is not respected; cannot debug due to React 19 RC being closed source
The text was updated successfully, but these errors were encountered: