Skip to content

[2.0 next, regressed after rc.13] Production refresh remains pending after a settled computation (production build) #3888

Closed

Description

@ethan-huo

Describe the bug

A production refresh stays pending even when its computation returns an already-resolved promise.

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, refresh, resolve } from "solid-js";
export default function App() {
  let calls = 0;
  const value = createMemo(() => Promise.resolve(++calls));
  const [result, setResult] = createSignal("idle");
  async function run() {
    await resolve(value); // The first computation has settled with 1.
    setResult("refreshing");
    setResult(String(await refresh(value))); // Production never reaches this write.
  }
  return (
    <>
      <button id="trigger" onClick={run}>
        Refresh
      </button>
      <output id="answer">{result()}</output>
    </>
  ); // Click: development shows 2; production remains refreshing.
}
  1. Paste this App into a fresh Solid 2 app. Build for production, click Refresh, and wait at least 200 ms.

Expected behavior

Expected: The output becomes 2, as it does in development.
Actual: The output remains refreshing in production.

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: production fail. rc.13 passes in both builds.

Additional context

Awaiting refresh is part of the public async action flow. A promise that never settles prevents the caller from completing.

Related: #3738, #3178

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 solid-js@2.0.0-rc.13 @solidjs/web@2.0.0-rc.13 @solidjs/signals@2.0.0-rc.13 @solidjs/compiler@2.0.0-rc.13 @solidjs/diagnostics@2.0.0-rc.13
bun add -d playwright
bun run link-head.ts /absolute/path/to/built/solid
BUILD_MODE=production 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.

Activity

  1. ryansolid commented on Oct 8, 2026

    @ryansolid
    Member

    Fixed on next in 5a26ebe (#3914).

    — Grok via Cursor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions