Bug/inconsistency with `dynamicIO` and client-side hooks in dynamic segment

[amannn]

Link to the code that reproduces this issue

amannn/nextjs-bug-repro-dynamicio-client-hooks@6f8f90d

To Reproduce

1. Clone https://github.com/amannn/nextjs-bug-repro-dynamicio-client-hooks/
2. Run pnpm dev and open e.g. http://localhost:300/en – works as expected
3. Run pnpm build – fails

Current vs. Expected behavior

I'm not sure what the expected behavior is, but at least aligning dev and prod seems like it should be the case.

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.22
  pnpm: 9.12.3
Relevant Packages:
  next: 15.0.4-canary.8 // Latest available version is detected (15.0.4-canary.8).
  eslint-config-next: 15.0.4-canary.8
  react: 19.0.0-rc-5c56b873-20241107
  react-dom: 19.0.0-rc-5c56b873-20241107
  typescript: 5.6.3
Next.js Config:
  output: N/A

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

dynamicIO

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

next dev (local), next build (local)

Additional context

No response

[cantemizyurek]

I been having these build errors too when I was experimenting with dynamicIO. Dev mode works as expected but when it comes to build things seem to fail unexpectedly.

[AkifumiSato]

Is there any progress on this issue?

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!