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

[2.0 next, regressed after rc.13] Loading on latest remains in fallback after a shared source settles

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

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

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

評価

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

調査の方向性

Start with the linked standalone reproduction, especially App.tsx and repro.test.ts, then run the documented Bun test against the same Solid build. Trace how the shared settled source is observed by both Loading boundaries. Done means the automated reproduction passes and both boundaries display 22 after clicking Load 2.

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

説明

Describe the bug

A Loading boundary using latest(id) keeps its fallback after the source shared by both boundaries has resolved.

Your Example Website or App

Standalone reproduction

Steps to Reproduce the Bug or Issue
  1. Use the source below with the selected Solid build (complete setup is linked above).
import { createMemo, createSignal, latest, Loading } from "solid-js";
export default function App() {
  let finish!: (value: number) => void;
  const replacement = new Promise<number>((resolve) => {
    finish = resolve;
  });
  const [id, setId] = createSignal(0);
  const data = createMemo(() => (id() ? replacement : Promise.resolve(1)));
  function load() {
    setId(1); // Replace the source shared by both boundaries.
    setTimeout(() => finish(2), 20); // Every async source is now settled.
  }
  return (
    <>
      <button id="trigger" onClick={load}>
        Load 2
      </button>
      <div id="answer">
        <Loading on={latest(id)} fallback="A">
          <span>{data()}</span>
        </Loading>
        <Loading fallback="B">
          <b>{data()}</b>
        </Loading>
      </div>
    </>
  ); // Wait for 11, then click: it stays A2 rather than becoming 22.
}
  1. Paste into a Solid 2 playground. Wait for 11, then click Load 2 and wait.
Expected behavior

Expected: Both boundaries display the final value: 22.
Actual: The first boundary keeps its fallback: A2.

Platform
  • Solid: solid-js / @solidjs/web next at 3086f1b77cd7b0431d3a7f768c2984c335758633; comparison 2.0.0-rc.13. Signals, compiler and diagnostics match the selected Solid build.
  • OS: macOS 26.6.2 (25G83); browser cases: system Google Chrome 155.0.8059.40. Server-only/type checks run in Bun 1.4.2.
  • Builds/comparison: development and production fail. rc.13 passes in both builds.
Additional context

Both Loading boundaries read the same settled source, so both should leave their fallback without another user update.

Related: #2706, #2829, #3524

Full automated reproduction

One-command setup, run and expected output.

Copy the standalone files into a fresh Bun project. The displayed snippet is executed by snippet.test.ts. The original automated case is also retained.

bun init -y
bun add [email protected] @solidjs/[email protected] @solidjs/[email protected] @solidjs/[email protected] @solidjs/[email protected]
bun add -d playwright
bun run link-head.ts /absolute/path/to/built/solid
BUILD_MODE=development bun test ./snippet.test.ts

The five linked packages must come from the same built HEAD checkout. Omitting the link step selects the rc.13 comparison. Chrome runs use the system installation.

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

環境構築

はじめの一歩

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

solidjs/solid のほかの issue

solidjs/solid の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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