[Bug]: `manifest.ts` breaks `HMR` in Next.js 16.2

[abhishekmardiya]

Link to the code that reproduces this issue

https://github.com/abhishekmardiya/hmr-cache-breakage-reproduction.git

To Reproduce

Using a manifest.ts file in Next.js 16.2 causes Hot Module Replacement (HMR) to stop working correctly.

After making code changes:

• HMR is not triggered
• UI does not update
• Even a hard reload (Cmd + Shift + R) does not reflect the latest changes

The only way to see updates is by deleting the .next build folder, after which the changes appear correctly.

---

Steps to Reproduce

1. Create a Next.js app using version 16.2
2. Add a manifest.ts file (App Router setup)
3. Start the development server (next dev)
4. Make any UI or code change

Current vs. Expected behavior

Expected Behavior

• HMR should trigger automatically
• UI should reflect the latest changes instantly
• Hard reload should always fetch the latest code

Current Behavior

• No HMR updates occur
• UI remains stale even after hard reload
• Changes only appear after deleting .next and restarting

Provide environment information

Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.4.0: Thu Mar 19 19:33:09 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T8112
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 24.14.1
  npm: 11.11.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.2.1 // Latest available version is detected (16.2.1).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Not sure

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

next dev (local)

Additional context

This issue did not occur before Next.js 16.2

• Removing manifest.ts restores normal HMR behavior
• Tested with the latest canary version (16.2.1-canary.10) as well — the issue still persists

@wbinnssmith

[Nithur-M]

For me, this HMR issue persists even without using manifest.ts. Just wanted to add it here.

[alexmarqs]

Same issue. I tried removing the manifest.ts but the HMR is still not working, it worked in a client component but in a server component not. Can't have a minimal repro at the moment, but I will try later if I can.

[abhishekmardiya]

Could you try removing the .next build after deleting manifest.json and check if the issue still persists?

[alexmarqs]

I confirm @abhishekmardiya, removing .next after deleting manifest.ts works

[nathanrogers6551-web]

Hi @abhishekmardiya, Just tried it — removing .next after deleting manifest.json fixed the issue for me as well. Thanks for the suggestion!

…

On Fri, Mar 27, 2026, 10:11 AM Alexandre Marques ***@***.***> wrote: *alexmarqs* left a comment (vercel/next.js#91981) <#91981 (comment)> I confirm @abhishekmardiya <https://github.com/abhishekmardiya>, removing .next after deleting manifest.ts works — Reply to this email directly, view it on GitHub <#91981?email_source=notifications&email_token=B7GH5FAAE5JOW4QXEILQ5KL4S2KZFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJUGMZTCMJXGMYKM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4143311730>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B7GH5FF4FXH2KAYKPI7QRDD4S2KZFAVCNFSM6AAAAACXBRNOFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNBTGMYTCNZTGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[PlagueFPS]

Wow, thank you for this. I was going insane trying to figure out where the regression was, can't believe it was the manifest.ts.

[icyJoseph]

This is fixed since https://github.com/vercel/next.js/releases/v16.2.3

Previous work around

Hi ya'll, we are looking into this right now.

In the mean time, you can run your dev server with --no-server-fast-refresh
And that'll unblock ya~