Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix Dev server is not restarting after running npm run build [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#84322•Fetched 2026-04-08 02:19:50
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
berinanieshberinaniesh
Participants
berinanieshberinanieshgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Error Message

Error: ENOENT: no such file or directory, open '/home/berinaniesh/tmp/test-app/.next/static/development/_buildManifest.js.tmp.9lyppmc6d9j' at ignore-listed frames { errno: -2, code: 'ENOENT', syscall: 'open', path: '/home/berinaniesh/tmp/test-app/.next/static/development/_buildManifest.js.tmp.9lyppmc6d9j' }

Root Cause

Dev server errors out because the files inside .next folder has changed. Ideally, it should detect changes in .next folder and restart.

Code Example

Error: ENOENT: no such file or directory, open '/home/berinaniesh/tmp/test-app/.next/static/development/_buildManifest.js.tmp.9lyppmc6d9j'
    at ignore-listed frames {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/berinaniesh/tmp/test-app/.next/static/development/_buildManifest.js.tmp.9lyppmc6d9j'
}

---

Operating System:
 Platform: Linux
 Arch: x64
 Version: Linux G513QY-arch 6.16.8-zen3-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Mon, 22 Sep 2025 22:08:18 +0000 x86_64 GNU/Linux
Binaries:
 Node: v24.8.0
 NPM: 11.6.1
Relevant Packages:
 next: 15.6.0-canary.33
 eslint-config-next: 15.6.0-canary.33
 react: 19.1.0
 react-dom: 19.1.0
 typescript: "^5"
Next.js Config:
 output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

gitlab.com:berinaniesh/nextjs-bugreport-reproducible-example

To Reproduce

  1. Start the dev server (npm run dev)
  2. Open another terminal and build the application (npm run build)

Current vs. Expected behavior

Dev server errors out because the files inside .next folder has changed. Ideally, it should detect changes in .next folder and restart.

The console shows

Error: ENOENT: no such file or directory, open '/home/berinaniesh/tmp/test-app/.next/static/development/_buildManifest.js.tmp.9lyppmc6d9j'
    at ignore-listed frames {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/berinaniesh/tmp/test-app/.next/static/development/_buildManifest.js.tmp.9lyppmc6d9j'
}

Provide environment information

Operating System:
 Platform: Linux
 Arch: x64
 Version: Linux G513QY-arch 6.16.8-zen3-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Mon, 22 Sep 2025 22:08:18 +0000 x86_64 GNU/Linux
Binaries:
 Node: v24.8.0
 NPM: 11.6.1
Relevant Packages:
 next: 15.6.0-canary.33
 eslint-config-next: 15.6.0-canary.33
 react: 19.1.0
 react-dom: 19.1.0
 typescript: "^5"
Next.js Config:
 output: N/A

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

Turbopack

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

next dev (local)

Additional context

Output type is standalone. Linux BTRFS with relatime in fstab (don't think it matters, but trying to give as much context as possible). Same issue is present on non canary and canary versions.

extent analysis

TL;DR

The issue can be mitigated by configuring Next.js to handle file system changes in the .next folder, potentially by using a different file system watching mechanism.

Guidance

  • Investigate the next configuration options to see if there's a way to specify a custom file watching mechanism that can handle changes in the .next folder.
  • Check if the relatime option in the fstab configuration for the BTRFS file system is causing issues with file system event detection.
  • Try using the --watch flag with the next dev command to see if it improves the detection of file system changes.
  • Consider updating the next version to a stable release, as the issue is present in both canary and non-canary versions.

Example

No specific code example is provided, as the issue seems to be related to the configuration and file system interaction.

Notes

The issue may be related to the file system watching mechanism used by Next.js, and configuring a custom mechanism may help mitigate the issue. However, without further investigation, it's difficult to provide a definitive solution.

Recommendation

Apply workaround: The best course of action would be to try configuring a custom file watching mechanism or using the --watch flag to see if it improves the detection of file system changes, as updating the next version may not necessarily resolve the issue.

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…
#pipeline error#runtime error#dependency conflict#environment setup#docker error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING