"Response.clone: Body already consumed" Error Returns After Node Upgrade
Unanswered
ej_xd. posted this in #help-forum
ej_xd.OP
Hi everyone,
I'm running into the "Response.clone: Body already consumed" error again and would appreciate any insights.
Background:
- Previously, this error appeared when deploying to Vercel using Next.js 14.2.14 and Node v20.
- Downgrading Node to v18.x and upgrading Next.js to 14.2.28 resolved the issue.
- Recently, Vercel started requiring Node v22 (since v18 is being deprecated), so we upgraded Node to v22.
- After this upgrade, the "Response.clone: Body already consumed" error started appearing again.
Has anyone else experienced this after upgrading to Node v22?
Any advice or workarounds would be greatly appreciated!
Thanks in advance!
I'm running into the "Response.clone: Body already consumed" error again and would appreciate any insights.
Background:
- Previously, this error appeared when deploying to Vercel using Next.js 14.2.14 and Node v20.
- Downgrading Node to v18.x and upgrading Next.js to 14.2.28 resolved the issue.
- Recently, Vercel started requiring Node v22 (since v18 is being deprecated), so we upgraded Node to v22.
- After this upgrade, the "Response.clone: Body already consumed" error started appearing again.
Has anyone else experienced this after upgrading to Node v22?
Any advice or workarounds would be greatly appreciated!
Thanks in advance!