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

Offen
#10,700 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
64/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
TypeScript
Sterne
1.8k
Forks
492
Ø Merge
1 T. 7 Std.
Gemergte PRs (30 T.)
357

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus clerk/javascript

Alle Issues in clerk/javascript

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.