Solid 2.0 reaches stable after five years, rebuilding async into its reactive core
by Paul

Solid 2.0 reaches stable after five years, rebuilding async into its reactive core

The SolidJS team has released Solid 2.0, the framework's second major version and the culmination of five years of work, the same span that separated creator Ryan Carniato's first commit from Solid 1.0. Planning for the rewrite began almost as soon as 1.0 shipped, with serious effort starting in late 2024 and a public roadmap in February 2025. The road to stable was deliberate: a beta in March, an API-frozen release candidate in August, and then 23 release candidates over 14 weeks, during which 971 pull requests were merged and 753 issues closed. The team set a single bar for stability, a full week with no regressions in ordinary app code and no crash or hang anywhere, with late-stage bug reports arriving from agents deliberately hunting edge cases in the scheduler.

The release's headline change is architectural: asynchronous operations now live inside the reactive graph itself. Computations can return Promises or async iterators and everything downstream “just understands”, letting the framework automatically handle race conditions and roll back speculative state while keeping the server the authority on truth. Server functions, which Solid's SolidStart metaframework pioneered in early 2022, have moved into the core with support for both RPC-style Request/Response calls and persistent connections over Server-Sent Events. That shift also enables a dramatic slimming of the API: primitives like createResource, batch, startTransition, on, produce, createComputed, and createMutable are all gone, along with the loading states, cancellation logic, and async ceremony they existed to manage. SolidStart itself has been retired, with the primitives to build metaframeworks now supplied by the core and framework-agnostic Vite plugins.

Solid 2.0 also leans explicitly into AI-assisted development. Rather than boasting about training-data familiarity, the team argues that a fine-grained graph “knows exactly what was read, where, and what will update”, so development builds now report reactive mistakes as they happen, with stable error codes, source locations, and suggested fixes, and can detect waterfalls, poorly constructed effect loops, and poorly scaling graph shapes. The same observability flows through to production via an updated Sentry plugin and integration with Chrome's Performance Tracks, while experimental syntaxes ReactiveScript and TSRX aim to make agent-authored code even more robust. The announcement frames the release as something of a baton pass for the broader signals movement, now standard in Angular, Svelte's runes, and Vue Vapor, and the subject of a TC39 proposal, with Solid aiming to carve “A path that others can follow. Deliberately this time”.

Paul
Written by Paul
Follow
Add as a preferred source on Google
SolidJS iconSolidJS
  9
  • ...

SolidJS is a declarative JavaScript library designed for building user interfaces. Unlike traditional frameworks that rely on a Virtual DOM, SolidJS compiles templates directly to real DOM nodes, ensuring efficient updates through fine-grained reactivity. By declaring state and utilizing it throughout the app, SolidJS ensures that only the necessary components update when state changes, optimizing performance.

Other apps mentioned in this article

No comments so far, maybe you want to be first?