Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix Intermittent missing chunk / React Client Manifest corruption in App Router on Windows after repeated server actions [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#91797•Fetched 2026-04-08 01:16:16
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
alanh511alanh511
Participants
alanh511alanh511github-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4closed ×1commented ×1issue_type_added ×1

Error Message

Error: Could not find the module "...next-devtools...segment-explorer-node.js#SegmentViewNode" in the React Client Manifest.

Code Example

### Provide environment information


Operating System:
  Platform: win32
  Arch: x64

Node.js:
  v24.13.0

Next.js:
  15.5.14

React:
  19.0.0

Package versions in app:

next: 15.5.14
react: 19.0.0
react-dom: 19.0.0
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

Private local app for now. I can provide a reduced repro if needed.

To Reproduce

To Reproduce

Environment:

  • Windows
  • Next.js 15.5.14
  • React 19.0.0
  • App Router
  • Prisma-backed local app
  • Repeated server-action form submissions on a single page with many forms/components

What I observed:

  1. Start the app locally.
  2. Use the App Router page with many server action forms rendered in a list/card layout.
  3. Perform repeated actions such as:
    • save run
    • retrieve
    • normalize
    • generate outputs
    • delete
  4. After a while, the app starts throwing runtime/build-artifact errors.
  5. At that point, localhost may begin returning 500s until .next is deleted and the app is rebuilt.

This happened multiple times during normal local use.

Current vs. Expected behavior

Expected:

  • App Router page should continue working normally after repeated server actions.
  • No missing chunk/module corruption should occur.

Current:

  • Runtime starts failing with missing chunk or React Client Manifest errors.
  • Localhost may return internal server errors.
  • Clearing .next, rebuilding, and restarting temporarily fixes it.

Provide environment information

### Provide environment information


Operating System:
  Platform: win32
  Arch: x64

Node.js:
  v24.13.0

Next.js:
  15.5.14

React:
  19.0.0

Package versions in app:

next: 15.5.14
react: 19.0.0
react-dom: 19.0.0

Which area(s) are affected? (Select all that apply)

React, Server Actions, Runtime

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

Include raw errors I saw variants of all of the following:

Cannot find module './778.js' Require stack:

  • ....next\server\webpack-runtime.js
  • ....next\server\pages_document.js
  • ...\node_modules\next\dist\server\require.js ... Cannot find module './611.js' Require stack:
  • ....next\server\webpack-runtime.js
  • ....next\server\app\page.js ... TypeError: webpack_modules[moduleId] is not a function TypeError: Cannot read properties of undefined (reading '/_app') Error: Could not find the module "...next-devtools...segment-explorer-node.js#SegmentViewNode" in the React Client Manifest. This is probably a bug in the React Server Components bundler. TypeError: a[d] is not a function Additional context This did not consistently look like an app-code logic failure. The app would often recover completely after:

stopping Node deleting .next running next build restarting

extent analysis

Fix Plan

To resolve the issue of missing chunk or React Client Manifest errors after repeated server actions, we'll focus on updating the next.config.js file and ensuring proper cache handling.

Step 1: Update next.config.js

Add the following configuration to prevent module caching issues:

module.exports = {
  //... other configurations ...
  experimental: {
    // Enable the new caching system
    cache: true,
  },
}

Step 2: Implement Cache Handling

Create a custom webpack.config.js file to handle cache issues:

module.exports = {
  //... other configurations ...
  cache: {
    type: 'filesystem',
    version: '1.0',
    cacheDirectory: path.resolve(__dirname, '.next/cache'),
  },
}

Step 3: Optimize Server Actions

Review and optimize server action code to prevent excessive re-renders and cache invalidation.

Verification

After applying these changes, restart the development server and repeat the steps that previously caused the issue. Verify that the app no longer throws runtime/build-artifact errors and that localhost does not return 500s.

Extra Tips

  • Regularly clean the .next directory to prevent cache buildup.
  • Monitor server action performance and optimize as needed to prevent excessive re-renders.
  • Consider upgrading to the latest version of Next.js and React to ensure you have the latest bug fixes and performance improvements.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING