SolidJS 2.0 ships stable, with server functions built into core
Solid's first major version in five years adds async to the reactive graph, retires the SolidStart metaframework, and trims its own API.
SolidJS 2.0 reached stable release this week, five years after Solid 1.0 shipped. The headline change is async as a first-class part of the reactive graph: a computation can now return a promise or an async iterator, and Solid handles the race conditions and rollback of speculative state itself.
Server functions move into the framework core, supporting both RPC-style calls and persistent Server-Sent Events connections, with reactive Server Components planned next. That covers most of what the separate SolidStart metaframework existed for, so the team retired it: every primitive needed to build a Solid metaframework now lives in core or in framework-agnostic Vite plugins. The API shrank too, dropping createResource, batch, startTransition, on, produce, createComputed and createMutable. Getting here took 23 release candidates in 14 weeks, 971 merged pull requests and 753 closed issues. Development builds also now report reactive mistakes with the exact file, line and fix, written as much for coding agents as for people.
Why it matters: this is a breaking major version, not a drop-in upgrade. SolidStart users in particular need to replan, since their metaframework will not move forward and the primitives it provided now live directly in Solid’s core. Anyone comparing frontend frameworks gets async data loading and server functions built in, rather than bolted on through a separate router or meta-layer.