Solid 2.0 Ships Stable With Async in Its Reactive Graph, Agent-Readable Diagnostics and Seven Removed APIs
Solid's JavaScript framework reached a 2.0.0 stable release on GitHub, five years after 1.0, adding async support to its reactive graph and a new diagnostics package.
Editor's Note ·
- Clarification:
- The article states that @solidjs/universal, @solidjs/html, @solidjs/h, @solidjs/element, @solidjs/diagnostics, @solidjs/compiler and @solidjs/babel-plugin were 'all tagged at version 2.0.0 within roughly two minutes of each other, close to 05:19 UTC on November 17.' This is accurate (GitHub's release data shows all seven tagged between 05:19:03 and 05:19:30 UTC that day), but it is not supported by any of the three sources cited in this article, which confirm only the @solidjs/diagnostics and solid-js tag times.
Overview
The Solid project tagged a stable [email protected] release on GitHub at 19:17 UTC on November 17, 2026, five years after Solid 1.0, according to the release notes. The notes describe the release, titled “v2.0.0 - The Long Hold,” as adding asynchronous support directly into Solid’s reactive graph and reworking the framework’s API surface. The release follows a 2.0.0-rc.15 release candidate previously covered by the Machine Herald in October, whose release notes at the time gave no date for a stable 2.0.
Async built into the reactive graph
According to the release notes, Solid 1.0 “bet on signals at a time when fine-grained reactivity was a rare position,” and the notes say that approach is now also found “in Angular, Svelte, Vue Vapor and a TC39 proposal.” The notes describe 2.0’s central change as bringing async directly into that reactive graph: a computation can return a Promise or an async iterator, and “everything downstream just handles it.” The release notes say race conditions are handled automatically, that optimistic state rolls back so the server remains the source of truth, and that a new live() function streams server functions to the client over persistent connections. The project’s changelog for the solid-js package lists the top-level change simply as “Async everywhere,” alongside an update described as “R3 based signals.”
A diagnostics package aimed at AI agents
The release notes frame the rebuilt internals as “Built to be written by agents,” saying the framework’s fine-grained graph “knows exactly what was read, where, and what will update,” and that development builds now report reactive mistakes with a stable error code, a source location and a suggested fix. The notes say the same graph can catch waterfalls, runaway effects and fan-out patterns that would not scale.
That framing is backed by a new package, @solidjs/diagnostics, also tagged at 2.0.0 on November 17. Its release notes describe it as an “agent-consumable diagnostics harness” built around a captureArtifact() function that records diagnostic and attribution data from a test scenario into a serializable artifact. The same notes list assertion helpers named expectNoDiagnostics, expectDiagnostic, expectRerunBudget and expectNoWaste, Vitest matchers shipped under @solidjs/diagnostics/vitest, and a browser bridge plus a Playwright adapter that capture the same diagnostic artifacts from running pages. An artifactToJSONL() function is described as providing line-oriented output for offline or agent analysis. The solid-js changelog adds that the core package now ships a bundled repair guide, at node_modules/solid-js/skills/reactivity-diagnostics/SKILL.md, that maps each diagnostic error code to its fix, and that a new DEV.diagnostics.setConsoleFooter() function prints a pointer to that guide the first time a given diagnostic code appears in the console.
A smaller, primitives-first API
The release notes describe Solid 2.0 as shipping “primitives, not a single blessed stack,” with what a metaframework needs now living in the core package and in framework-agnostic Vite plugins, so that developers can bring their own router and cache. At the same time, the notes say the API surface has shrunk: createResource, batch, startTransition, on, produce, createComputed and createMutable have all been removed, a change the notes summarize as “Safe by construction rather than by exhaustion.”
The path from release candidate to stable
According to the release notes, the “Road to 2.0” was announced in February 2025, followed by a beta and then a release candidate phase. Once the API was frozen, the project shipped 23 release candidates over 14 weeks, merging 971 pull requests and closing 753 issues in that span. The notes say the bar the team set for declaring the release stable was “a full week with no regression in ordinary app code, and no crash or hang anywhere.”
Seven supporting packages — @solidjs/universal, @solidjs/html, @solidjs/h, @solidjs/element, @solidjs/diagnostics, @solidjs/compiler and @solidjs/babel-plugin — were all tagged at version 2.0.0 within roughly two minutes of each other, close to 05:19 UTC on November 17, according to GitHub’s release timestamps; the flagship [email protected] tag followed about 14 hours later, at 19:17 UTC the same day. The release notes do not explain the gap between the two batches.
What the release notes don’t say
The release notes point developers who are not ready to move to the 1.x branch of the repository, to the solid-js@v1-latest npm tag, and to documentation at v1.solidjs.com. They do not give adoption figures, a timeline for when any particular downstream framework or tool will require 2.0, or a breakdown of how many of the 971 merged pull requests were bug fixes versus new features.