Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix Dev server randomly doesn't trigger refresh [5 comments, 4 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#86306•Fetched 2026-04-08 02:11:34
View on GitHub
Comments
5
Participants
4
Timeline
10
Reactions
1
Author
nmoreaudnmoreaud
Participants
icyJosephicyJosephmischnicmischnicNick98-1Nick98-1nmoreaudnmoreaud
Timeline (top)
commented ×5labeled ×2subscribed ×2issue_type_added ×1

Code Example

pnpm create next-app@latest testnext --yes
cd testnext
pnpm approve-builds
pnpm run dev

---

h1 {
  color: #2aaaaa;
}

---

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 16338
  Available CPU cores: 4
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.22.0
Relevant Packages:
  next: 16.0.2-canary.24 // Latest available version is detected (16.0.2-canary.24).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/nmoreaud/next-dev-server-refresh-bug

To Reproduce

pnpm create next-app@latest testnext --yes
cd testnext
pnpm approve-builds
pnpm run dev

Edit global.css, add:

h1 {
  color: #2aaaaa;
}

Then open http://localhost:3000/ in a web browser, and modify the h1 color a few times in global.css. Approximately once every three modification, the display isn't updated, and the line "✓ Compiled in XXms" doesn't appear in the terminal.

Current vs. Expected behavior

The web browser display isn't up to date, and F5 doesn't fix the problem. If I stop the dev server and restart it, the modification is taken into account.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 16338
  Available CPU cores: 4
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.22.0
Relevant Packages:
  next: 16.0.2-canary.24 // Latest available version is detected (16.0.2-canary.24).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
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

Same pb with Firefox and Chrome.

Very hard to reproduce with npx create-next-app -e reproduction-template, though it happened once.

extent analysis

TL;DR

The issue can be temporarily resolved by stopping and restarting the development server after modifying the global.css file.

Guidance

  • The problem seems to be related to the Turbopack feature in Next.js, which is used for development server refresh.
  • To verify the issue, try modifying the global.css file multiple times and check if the changes are reflected in the browser.
  • As a workaround, stop the development server and restart it after making changes to the global.css file to ensure the updates are applied.
  • Try to reproduce the issue using the reproduction template provided by Next.js to see if it's a specific project issue or a general problem with the Turbopack feature.

Example

No specific code snippet is provided as the issue seems to be related to the development server configuration rather than a specific code block.

Notes

The issue is difficult to reproduce consistently, and it may be related to the specific project setup or the Turbopack feature in Next.js. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply workaround: Stop and restart the development server after making changes to the global.css file, as this seems to resolve the issue temporarily. This workaround is recommended because it provides a reliable way to ensure that changes are applied, even if it's not a permanent fix.

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…
#dependency conflict#environment setup#docker error#permission error#memory optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Dev server randomly doesn't trigger refresh [5 comments, 4 participants]