Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

クローズ
  • 何か問題がありますか？
#3,797 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
58/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
frontend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
TypeScript
スター
36.1k
フォーク
1.1k
平均マージ
13時間 13分
マージ済み PR（30日）
306

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

solidjs/solid のほかの issue

solidjs/solid の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。