Solid 2.0 brings async reactivity and AI-agent diagnostics to core
Solid 2.0 is now stable, according to the Solid project announcement and iThome. It integrates asynchronous results into its reactivity graph, coordinates requests with UI updates to reduce stale-data race conditions, moves server functions into the core, and adds diagnostics and repair guidance for AI coding agents. The release also removes createResource, batch, and startTransition, while SolidStart is retired in favor of framework-agnostic Vite plugins and a Start mode.
The release gives web developers built-in handling for asynchronous UI state and provides AI coding agents with structured diagnostics, while introducing migration work for existing Solid applications.
5 years is a long time to work on anything. It took 5 years from my first commit of Solid to 1.0, and it's been another 5 since then.
A lot changes in 5 years. Solid 1.0 made a bet that fine-grained reactivity, signals, was the right foundation for building user interfaces. Back then it was an unusual position. Today signals are everywhere. In Angular, in Svelte's runes, in Vue Vapor, and in a proposal before TC39 to put them in the language itself. It even pushed the conversation into React's compiler.
More recently that conversation has shifted to AI, arguably an even larger change in how we build. But Solid has always been about building the right things; the performant things. So for us the mission hasn't really changed all that much. The things that we identified as standout about our approach still stand out now. But instead of living in the shadow of more popular solutions Solid 2.0 carves out a path that others can follow. Deliberately this time.
Today that solution reaches stable.
#Solid#SolidStart#SolidStart Start mode#Sentry#Angular#Svelte#Vue