Solid 2.0
- ID
- 47977
- Status
- summarized
- Published
- 18 Nov 2026, 2:56 AM
- Fetched
- 19 Nov 2026, 3:02 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://www.solidjs.com/blog/solid-2-0-the-long-hold/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.0
- Created
- 19 Nov 2026, 3:03 AM
- Tags
- Audience
- developersvibe_codersai_agent_users
What happened
Solid 2.0 has reached stable five years after Solid 1.0, with async moved into the reactive graph: computations can return Promises or async iterators, and speculative state rolls back automatically. Server functions are now in Solid core, supporting RPC over Request/Response and persistent connections via Server Sent Events, alongside diagnostics built for agents and a smaller API. The Hacker News thread has 366 points and 114 comments.
Why it matters
If you maintain a Solid or SolidStart app, this is a migration decision: test whether async memos and the core server-function live/SSE API replace your existing data-fetching layer, and check the smaller API for breaking changes. If you are not on Solid, the release is a concrete reference for where signals are heading—Angular, Svelte runes, Vue Vapor, and a TC39 proposal are cited—but it does not require action this week.
Discussion angle
Does putting async and server functions into the reactive core make separate data-fetching/cache layers redundant, or does it just move complexity—and what would a realistic Solid 1.x-to-2.0 migration checklist look like?