Cached components when using 'use cache' / dynamicIO in dev mode

[cornedor]

Summary

Is there a way to (partially) disable dynamicIO cache in dev mode. I'm building components where I've already implemented the cache. It has a long cache life and cache tags, so it is cached for a long time. But when I change the code of my component, the cached version is still served.

Is this working as intened? And if so, is there a workaround?

Additional information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:25 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6020
  Available memory (MB): 65536
  Available CPU cores: 12
Binaries:
  Node: 22.16.0
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.4.0-canary.126 // Latest available version is detected (15.4.0-canary.126).
  eslint-config-next: 15.4.0-canary.126
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

Example

No response

[icyJoseph]

How have you implemented this? Could you share some pseudocode, or repo?

[cornedor]

Hmm, it seems to be browser cache, and only be an issue in Firefox. (or at least it works fine in Chrome)

[icyJoseph]

Rather, it is like, if / is open, then the other route refreshes correctly 🤔 if there's no tab with /, then only hard refresh works

[icyJoseph]

Did you verify that the / route has to be open for the code changes to reflect? I am a bit busy right now, I couldn't verify much more.

[cornedor]

Yes, you are right. It indeed also works fine when the component is open at the / route.

For now, I'm working with the browser devtools and cache disabled open, and that also works fine.

[icyJoseph]

A PR up to fix this issue :)