
Tech • AI • Robotics • Game
⏱ ≈ 3 min read · 6-min video — 3 min saved
Solid 2.0 has launched with a redesigned reactive model that treats asynchronous data like ordinary state, aiming to simplify front-end development by removing loading-state boilerplate, reducing race conditions, and folding more server and tooling features into the core framework.
Ryan Carniato released Solid 2.0 on Monday, marking the framework’s first major version since Solid 1.0 arrived in 2021. The update follows a long beta cycle and positions Solid as a more opinionated and consolidated alternative in the JavaScript framework market.
Solid keeps its core approach of running a component function once and then updating only the exact DOM nodes affected by state changes. That behavior is driven by signals, a reactive primitive that later spread across the broader ecosystem, including concepts adopted in Angular, Vue, and a TC39 proposal for JavaScript itself.
The biggest change in Solid 2.0 is that computations can now return promises, allowing asynchronous data to flow through the same system as synchronous signals. In practice, developers can fetch data inside a normal memo and consume it in JSX as if it were any other value, while the framework automatically waits for unresolved dependencies.
This redesign is aimed at common front-end problems such as chained async requests, UI loading flags, and stale responses arriving out of order. When one async value depends on another, Solid 2.0 can handle waiting and cancellation automatically, reducing the amount of manual code typically needed to manage request sequencing.
The release also cuts back legacy abstractions created to compensate for the older synchronous model. A widely used data-fetching function from Solid 1 was removed along with six other primitives, reflecting a broader effort to simplify the framework by eliminating workarounds that are no longer necessary.
Solid Start, the framework’s official meta-framework, has effectively been retired after key features were absorbed into Solid itself. Most notably, server functions, which Solid Start introduced in 2022, now live in the main framework, leaving developers free to pair Solid with the router of their choice rather than relying on a tightly coupled full-stack layer.
The deletions and architectural changes mean upgrading existing Solid 1 applications may require substantial refactoring. The release is designed with automated assistance in mind, reflecting the growing use of coding agents and AI-assisted migration workflows in modern JavaScript development.
When runtime errors occur, Solid 2.0 provides an error code, the exact location, a suggested fix, and a path to a skill.md file intended to guide automated agents through the repair. The framework also uses its knowledge of state reads and pending updates to detect issues such as request waterfalls and improperly implemented effect loops before they become production failures.
The 2.0 beta landed in March and was followed by 23 release candidates, 971 pull requests, and 750 closed issues before the stable release. Some late bug reports came from automated agents stress-testing scheduler edge cases, and the team did not declare the release stable until an entire week passed without a regression.
Solid 2.0 is a significant architectural rewrite centered on making asynchronous state feel native rather than bolted on. The release underscores a broader shift in front-end development toward finer-grained reactivity, fewer framework layers, and tooling increasingly built for both developers and software agents.
Ask a question