@clerk/nextjs: Pages Router builds bundle next/headers into the client via the App Router provider
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nextjs, react, typescript
- Domain
- build-system, frontend
Research direction
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.
Written by the indexing model from the issue text.
Description
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.jsimports bothapp-router/client/ClerkProviderandpages/ClerkProvider, and picks one at runtime withnext/compat/router. Both are bundled.app-router/client/ClerkProvider.jsimportsinvalidateCacheActionfromapp-router/server-actions.js.server-actions.jsis a"use server"file that importscookiesfromnext/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:
- Create a Pages Router app with
ClerkProviderinpages/_app.tsx. - Run
next build. - Search
.next/static/chunksforRequestCookiesAdapterorResponseCookies.
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 innext/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)
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 492
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 374
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from clerk/javascript
-
<SignIn />: the reset password code step renders an empty, focusable back button with no accessible namePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
clerk/javascript#10708 ·
Maintainers usually reply within 1 day
-
Built-in reverification dialog lacks an accessible name (aria-dialog-name)Possibly taken @ItsShivam05 claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
clerk/javascript#10548 ·
Maintainers usually reply within 1 day
-
MFA enrollment QR SVG lacks an accessible name (svg-img-alt)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
clerk/javascript#10547 ·
Maintainers usually reply within 1 day
-
<SignIn />: first "Use email" click switches back to phone when `initialValues.phoneNumber` is setPossibly taken @twicestruck claimed this 22 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
clerk/javascript#10487 ·
Maintainers usually reply within 1 day
-
useLoadedIsomorphicClerk misses "ready" when a ClerkProvider remounts after clerk-js has loaded — <ClerkLoading> never resolvesMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
clerk/javascript#10462 ·
Maintainers usually reply within 1 day
All issues in clerk/javascript
Similar issues
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day