@clerk/nextjs: Pages Router builds bundle next/headers into the client via the App Router provider

Aperta
#10,593 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
nextjs, react, typescript

Direzione di ricerca

Start with the import chain: dist/esm/client-boundary/ClerkProvider.js loads both the App Router and Pages Router providers, and app-router/server-actions.js is a "use server" file that imports cookies from next/headers. Build a minimal Pages Router app with ClerkProvider in pages/_app, run next build, and search .next/static/chunks for RequestCookiesAdapter. Done means the client chunks no longer contain next/headers, and the App Router path still works. The maintainers have not chosen between an opt-in entry point and lazy loading, so confirm the approach first.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

This issue was written by Claude Code, but verified by me.

Reproduction

No separate repo. It shows up in any Pages Router app that renders ClerkProvider from @clerk/nextjs: build it and search the client chunks for Next's cookie code (e.g. RequestCookiesAdapter).

Publishable key

N/A. The problem is in the build output, not the instance.

Description

In a Pages Router app, ClerkProvider adds Next's server request code to every route's client JS: cookies, headers, draft mode and the edge cookie parser. In our app that's 18.5 KB gzipped per route.

The import chain, in @clerk/nextjs 7.4.3:

  • dist/esm/client-boundary/ClerkProvider.js imports both app-router/client/ClerkProvider and pages/ClerkProvider, and picks one at runtime with next/compat/router. Both are bundled.
  • app-router/client/ClerkProvider.js imports invalidateCacheAction from app-router/server-actions.js.
  • server-actions.js is a "use server" file that imports cookies from next/headers.

An App Router build turns that file into a server-action reference. A Pages Router build has no server-action boundary, so the file and the whole next/headers graph land in the client bundle.

Steps to reproduce:

  1. Create a Pages Router app with ClerkProvider in pages/_app.tsx.
  2. Run next build.
  3. Search .next/static/chunks for RequestCookiesAdapter or ResponseCookies.

Expected behavior:

A Pages Router app's client bundle doesn't include next/headers.

Actual behavior:

Every route's client bundle includes next/headers and the request code behind it.

Workaround:

We alias next/headers to a stub in the browser only:

// next.config.ts
turbopack: {
  resolveAlias: {
    'next/headers': { browser: './src/utils/next-headers-browser.ts' },
  },
},

The stub exports cookies, headers and draftMode, each of which throws if called. Nothing calls them, since the App Router provider never renders under the Pages Router.

Possible fixes:

Bundling both providers makes sense for apps that mix routers. For Pages-only apps, either of these would avoid it:

  • An opt-in Pages Router entry point that doesn't import the App Router provider.
  • Load the App Router provider, or just invalidateCacheAction, lazily, so a Pages Router build doesn't pull in next/headers.
Environment
System:
  OS: macOS 26.6.2
  CPU: (12) arm64 Apple M2 Pro
Binaries:
  Node: 24.15.0
  pnpm: 12.16.1
npmPackages:
  @clerk/nextjs: ^7.4.3 => 7.4.3
  @clerk/shared: ^4.15.0 => 4.15.0
  next: 16.4.2 => 16.4.2
  react: 19.2.6 => 19.2.6
  react-dom: 19.2.6 => 19.2.6
Bundler: Turbopack (next build)
Lingua principale
TypeScript
Stelle
1.8k
Fork
492
Merge medio
1g 8h
PR unite (30g)
374

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di clerk/javascript

Tutte le issue di clerk/javascript

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.