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
next@v15.0.0-canary.99 added a new
reactMaxHeadersLength
option tonext.config.js
.It was introduced in this PR: https://github.com/vercel/next.js/pull/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 added in https://github.com/facebook/react/pull/27641.
It ultimately gets used here via
remainingCapacity
.One theory is that this functionality doesn't play nicely with our use of a
TransformStream
: https://github.com/netlify/next-runtime/blob/f10d6611921fe355f33804f394eb25678cbedd85/src/run/handlers/server.ts#L135.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