@clerk/nextjs ≥ 7.9.24: module-level displayName mutation breaks App Router PPR resume ("Expected the resume to render <ClerkProvider> … <ReactClerkProvider>")

Open
#10,700 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@marcvive is already working on this.

Since Nov 11, 2026.

  • #10773 by @marcvive — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active

Research direction

Start with dist/esm/pages/ClerkProvider.js and trace how components.client.js and client-boundary/ClerkProvider.js load it alongside the App Router provider. Compare the 7.9.23 and 7.9.24 behavior around ReactClerkProvider.displayName, then run the linked reproduction’s build and request the page twice. Done means both requests resume the prerendered shell without the component-name mismatch or client-render fallback.

Written by the indexing model from the issue text.

Description

needs-triage
Preliminary Checks
Reproduction

https://github.com/marcvive/clerk-ppr-resume-repro

Publishable key

pk_test_ZGVsaWNhdGUtYmx1ZWpheS05NDQwLmNsZXJrLmFjY291bnRzLmRldiQ

Description

Since 7.9.24, App Router apps using Partial Prerendering (cacheComponents: true) fail to resume their prerendered shell once a client component importing Show from @clerk/nextjs has been loaded on the server. The route falls back to client rendering on every request after that.

Steps to reproduce:

  1. Clone the reproduction, cp .env.local.example .env.local and add the keys of a development instance.
  2. npm install && npm run build && npm start
  3. Request the page twice: curl -s http://localhost:3200/ > /dev/null (twice).

Expected behavior:

Both requests resume the prerendered shell without errors — as they do on @clerk/nextjs 7.9.23 (same repro, npm install @clerk/[email protected] --save-exact, rebuild).

Actual behavior:

The first request is fine. Every later request logs on the server:

Error: Expected the resume to render <ClerkProvider> in this slot but instead it rendered <ReactClerkProvider>. The tree doesn't match so React will fallback to client rendering.

and the browser logs minified React error #419. In our real app this fails our Playwright E2E suite; pinning 7.9.23 fixes it.

Root cause:

In 7.9.24, dist/esm/pages/ClerkProvider.js moved ReactClerkProvider.displayName = "ReactClerkProvider"; from inside the Pages Router ClerkProvider render function to module top level. ReactClerkProvider is InternalClerkProvider from @clerk/react/internal — the same component object the App Router provider (app-router/client/ClerkProvider.js) renders, and which @clerk/react names "ClerkProvider".

components.client.js → client-boundary/ClerkProvider.js imports ../pages/ClerkProvider unconditionally, and Show / ClerkProvider are re-exported from #components (= components.client.js). So the provider's name depends on load order: the build-time prerender records <ClerkProvider> in the postponed state; once a client component using Show is loaded on the server, every resume sees <ReactClerkProvider>. React's resume check compares component names (displayName || name), so it throws.

Hooks such as useAuth alone don't trigger it, because the package is "sideEffects": false and they never load components.client.js.

Suggested fix:

Don't mutate the shared component's displayName: move the assignment back inside the Pages Router render, or wrap the provider in a separately named local component.

Workaround: pin @clerk/[email protected].

Environment
System:
    OS: Windows 11 10.0.26200
    CPU: (8) x64 Intel(R) Core(TM) Ultra 7 258V
    Memory: 10.15 GB / 31.57 GB
  Binaries:
    Node: 24.22.1 - C:\Program Files\nodejs\node.EXE
    npm: 11.19.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 156.0.8078.80
    Edge: Chromium (152.0.4191.53)
    Firefox: 159.0.1 - C:\Program Files\Mozilla Firefox\firefox.exe
  npmPackages:
    @clerk/nextjs: 7.9.25 => 7.9.25
    next: 16.4.5 => 16.4.5
    react: 19.3.1 => 19.3.1
    react-dom: 19.3.1 => 19.3.1
Dominant language
TypeScript
Stars
1.8k
Forks
492
Avg merge
1d 8h
Merged PRs (30d)
374

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from clerk/javascript

All issues in clerk/javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.