Back to Daily Feed 
SolidJS 2.0 RC.20: Key Fixes for Signals & Hydration
Worth Reading
Originally published on SolidJS Releases
View Original Article
Share this article:
Summary & Key Takeaways
isPendingfor derived store keys no longer incorrectly reads true on first landing.- Derived stores reading async memos through
latest()now show correct values immediately. - Render effects reading errored-then-recovered derived stores now re-run as expected.
- The 'multiple instances of Solid' warning is now more accurate, firing only when instances actually interact.
- Hydrated
<Errored>boundaries no longer log 'Hydration key miss' for lazily created content.
Our Commentary
Solid's RC releases are always packed with deep, technical fixes. I appreciate the precision in addressing these edge cases around reactivity and hydration. It shows a commitment to robustness that I think is often overlooked in the rush for new features. The improved 'multiple instances' warning is a small but welcome DX win.
View Original Article
Share this article: