Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[2.0 RC] SSR hydration keys shift when memo()-wrapped prop getters are read before `children` through `<Dynamic>`, so the child never hydrates

Aperta
  • Qualcosa non va?
#3,797 0 commenti 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
58/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
frontend

Direzione di ricerca

Start by tracing server-side ssrElement prop processing and how hydration keys are allocated for children; compare those allocations with the client behavior described in the report. Use the linked StackBlitz reproduction and run its install, build, and render commands, then serve build/ and toggle the signal. Done when the child claims the matching server key and updates the in-document span.

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

Descrizione

Describe the bug

A component rendered through <Dynamic component="button"> can receive props whose values are ternaries over a logical expression. The compiler emits these as memo(() => …)() ? a : b getters. On the server, each read of such a getter creates a sync memo, and that memo takes a child id from the owner that is current during ssrElement's prop loop. That owner is the same one that later allocates the hydration key for the element's children. The getters are read before children, so the server's key for the child is shifted by the number of memo-wrapped props. The client doesn't make the same allocations, so it looks for the unshifted key.

As a result, the child misses hydration. The client builds a detached copy, the server-rendered node stays in the document with nothing bound to it, and later reactive updates to the child never reach the page.

We first saw this with Kobalte 2.0.0-alpha.2's Dialog.Trigger / DropdownMenu.Trigger (Button → Polymorphic → Dynamic). The repro below doesn't use Kobalte; it only copies Kobalte's prop layering.

Your Example Website or App

https://stackblitz.com/edit/solidjs-templates-gftulnlj?file=package.json

Steps to Reproduce the Bug or Issue
  1. npm install && node build.mjs && node render.mjs
  2. Serve build/ statically and open index.html.
  3. In the console, run toggle().
Expected behavior

Expected behavior:
The server gives the child the key that follows the button's key, matching the client:

<button _hk=50 type="button"><span _hk=51 id="label">label</span></button>

The client claims <span _hk=51>, and after toggle() the in-document span gets data-on.

Actual behavior:
The server skips three ids before the child:

<main _hk=0><button _hk=50 type="button"><span _hk=54 id="label">label</span></button></main>

The client (development build) warns:

Hydration key miss for "51": no server-rendered element carries this key (template: <span id=label>label). A detached element was created instead; its subtree will not appear in the document or become interactive. …
Hydration completed with 1 unclaimed server-rendered node(s): <span _hk="54" id="label">label</span>

After toggle(), the span in the document is still _hk="54" with no data-on. The update went to the detached client copy.

Screenshots or Videos

No response

Platform
  • OS: macOS
  • Browser: Chrome
  • Version: Version 154.0.8037.97 (Official Build) (x86_64)
Additional context

None.

Lingua principale
TypeScript
Stelle
36.1k
Fork
1.1k
Merge medio
10h 7m
PR unite (30g)
289

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 solidjs/solid

Tutte le issue di solidjs/solid

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.