Error when using namespace/compound components in React Server Component

Link to the code that reproduces this issue

https://github.com/DanielGiljam/nextjs-rsc-jsx-issue

To Reproduce

1. Start the application in development (next dev)

2. See the error

   React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
   

Current vs. Expected behavior

Current behavior: you get the error described above.

Expected behavior: namespace/compound components would work like they do in client components.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 23.3.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.14.2
Relevant Packages:
  next: 15.2.0-canary.19 // Latest available version is detected (15.2.0-canary.19).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A

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

Module Resolution, Not sure

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

next dev (local), next build (local)

Additional context

No response

Start with the reproduction repository linked in the issue and run it with next dev, then next build, to confirm the namespace/compound component error. Trace the module-resolution and React Server Component handling involved in the failing import; done means the reproduction works in both stages as it does for client components.