Config returns null in production build (Next.js 16 + Turbopack RSC)

Describe the Bug

PayloadCMS Config Returns null in Production Build (Next.js 16 + Turbopack)

Environment

• PayloadCMS: 3.73.0 (latest, with Next.js 16 support)
• • Next.js: 16.2.0-canary.17 (meets >16.1.1-canary.35 OR 16.2.0+ requirement)
• • • React: 19.2.4
• • • • Runtime: Bun 1.3.8 (also reproduced with Node 22)
• • • • • Database: PostgreSQL via @payloadcms/db-postgres
• • • • • • Bundler: Turbopack (Next.js 16 default)
• • • • • • • Build Target: Docker production build

Summary

When running PayloadCMS in a Next.js 16 production build with Turbopack, the Payload config object returns null when imported in React Server Component context, specifically in the (payload)/layout.tsx file. This causes the admin panel to fail with an RSC error.

Error occurs ONLY:

Link to the code that reproduces this issue

N/A (Reproduction steps provided below)N/A (Reproduction steps provided below)

Reproduction Steps

See the 'Describe the Bug' section above for full reproduction details and code blocks.

Which area(s) are affected?

area: core

Environment Info

PayloadCMS: 3.73.0, Next.js: 16.2.0-canary.17, React: 19.2.4, Bun: 1.3.8, Bundler: Turbopack