Ref gets lost during Suspense execution

Why this is a good first issue

Issue involves React Suspense behavior and ref handling during SSR.

AI Summary

The issue reports ref values being lost during Suspense execution in SSR mode, with a provided reproduction case. It requires understanding of both React's Suspense behavior and Next.js SSR implementation. The maintainer comment suggests this may be expected React behavior rather than a Next.js bug.

Issue Description

Link to the code that reproduces this issue

https://github.com/nirus/nextjs-ref-ssue

To Reproduce

Clone the application
Run the application is SSR debug mode in Vs-code (launch.json)
Observe the console.log in terminal window

Current vs. Expected behavior

useModuleImportSuspense throws the promise and cause the SSR to suspend and refs loose the value on subsequent rendering when resolved.

Current Behaviour: HELLO THERE ---> false HELLO THERE ---> false ..(loop)

Expected Behaviour HELLO THERE ---> false HELLO THERE ---> true

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:25 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T8110
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.11.0
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.3
Next.js Config:
  output: N/A

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

Lazy Loading, Performance

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

next dev (local), next build (local)

Additional context

GitHub Labels

bugLazy LoadingPerformance