You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[2.0 / next] createOptimisticStore(fn) swallows the error when fn reads a failed async memo (createStore delivers it) #4437
A derived createOptimisticStore(fn, [], { key }) whose fn reads an async createMemo never reports that memo's rejection: readers keep the last value, with no error and no pending. The same fn under createStore delivers the error, and so does createOptimisticStore when fn awaits the promise itself.
Found at next5e68925 (2.0.0-rc.20): a ReactiveScript app's list, after a failed reload, stayed on its old rows (or its Loading fallback) instead of showing the Errored fallback.
Activity
eval: round 7: the createOptimisticStore error bug is solidjs/solid#4437
chore(size): record #4437's sizes over next @ 7135a77
fix(signals): createOptimisticStore(fn) passes an upstream memo's err…
ryansolid commentedon Oct 30, 2026
Fixed on
nextby #4457 (5315127); it ships in the next RC.Generated by Claude Code