1 person reported

All time, since Sep 27.

Reused fetch options lose next config

Sharing one module-level fetch options object between two fetches with Cache Components enabled can break prerendering.

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/next-js/issues/4178/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 3 a week at the late-September peak.

Reused fetch options object loses next config on second call.

Is this your bug?

Where: fetch caching
Versions: 16.4.0-canary.48
Platforms: macOS
How bad: Breaks a normal workflow.

Original reports3, newest first

Sep 27, 2026Reusing fetch options removes next configuration and can break prerenderingOn GitHub#99330
Sep 27, 2026Reusing fetch options removes next configuration and can break prerenderingOn GitHub#99328
Sep 27, 2026Reusing fetch options removes next configuration and can break prerenderingOn GitHub#99326

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.