This is a minimal Next.js App Router reproduction for a tenant component
factory that creates next/dynamic components from a computed import path.
npm install
rm -rf .next
npm run dev -- --turbopackOpen http://localhost:3000/demo
The page can return HTTP 200 while the server reports that a client-reference module was instantiated but its module factory is unavailable when Cache Components are enabled.
Doing a full route reload with no cache does not result in the same behavior.
| Variant | Next version | Result |
|---|---|---|
| Static provider; dynamic navbar (Turbopack dev) | 16.3.0 | Factory error (redacted; client-reference module factory unavailable) |
| Literal provider import; dynamic navbar (Turbopack dev) | 16.3.0 | Factory error (redacted; client-reference module factory unavailable) |
| Fully dynamic fixture; Cache Components off (Turbopack dev) | 16.3.0 | No error |
| Fully dynamic fixture; Cache Components on (Webpack dev) | 16.3.0 | No error |
| Fully dynamic fixture; Cache Components on (Webpack production build) | 16.3.0 | No error |
| Fully dynamic fixture; Cache Components on (Turbopack dev) | 16.3.1-canary.1 | Factory error (redacted; client-reference module factory unavailable) |
| Fully dynamic fixture; Cache Components on (Turbopack production build/start) | 16.3.1-canary.1 | No error |
- Next.js:
16.3.1-canary.1 - React:
19.2.8 - React DOM:
19.2.8 - Bundler: Turbopack
- Cache Components: enabled