Solid 2.0 Ships Stable With Seven APIs Removed, and the Post Publishes No Benchmark
Software / news
Solid 2.0 Ships Stable With Seven APIs Removed, and the Post Publishes No Benchmark
The Nov. 17 release deletes createResource and batch, requires Node 22.12, and a patch release followed within a day. Ryan Carniato's announcement gives no bundle size or speed figure.
Solid 2.0 is stable. The release was tagged on Nov. 17, 2026, and it deletes seven APIs that Solid 1.x users have written against for years, among them createResource, batch and startTransition.
The announcement, "Solid 2.0 - The Long Hold", is by Ryan Carniato and is dated Nov. 16, a day before the tag on the solidjs/solid releases page. This is a read of the release notes, not a test: I have not run 2.0 on a real application.
What Solid 2.0.0 removes
The release notes list these removals and runtime changes. The post itself names the seven removed APIs but includes no full migration guide.
| Change | Detail from the release notes |
|---|---|
| Removed APIs | createResource, batch, startTransition, on, produce, createComputed, createMutable |
| Runtime | Node 22.12 or later; ESM only, no .cjs builds |
| Event attributes | Only on plus an uppercase letter is a handler; onclick becomes a plain attribute |
| Dev builds | Renamed *.dev.js, which breaks deep imports of dist/dev.js |
| Observability | DEV.diagnostics moved to OBSERVE |
The replacement for createResource is async inside the reactive graph. A memo can return a Promise or an async iterator, and downstream code handles the pending state. The post says speculative state is rolled back automatically, so the server stays the source of truth.
The 23 release candidates
Carniato says serious work began in late 2024, the road to 2.0 was announced in February 2025, the beta arrived in March and the release candidate in August with the API frozen. For the release-candidate stretch he counts 23 candidates over 14 weeks, with 971 pull requests merged and 753 issues closed.
- Release candidates23 items
- Issues closed753 items
- Pull requests merged971 items
Source: Solid 2.0 - The Long Hold, solidjs.com, accessed 2026-11-19
The bar for calling it stable was "A full week with no regression in ordinary app code, and no crash or hang anywhere." A patch followed anyway. Solid 2.0.1 landed on Nov. 18 and fixes a hydrate(document) call that hung, a delegated handler that failed to run when the same Event was dispatched twice, and nested <Portal> ordering that now matches 1.x.
Server functions in core, SolidStart retired
Server functions, introduced in SolidStart in early 2022, now live in core. The post says they support RPC over Request and Response and persistent connections over Server-Sent Events. Carniato says reactive Server Components will be announced in the coming weeks, with no date.
The post also says "We retired our metaframework SolidStart." InfoQ reported on Sept. 19 that SolidStart 2.0 had reached stable on Vite 8 for Solid 1.x, then entered maintenance mode days later. InfoQ says the team chose to retire it rather than ship a hollow 3.0, since its remaining role was wrapping features that moved into core. SolidStart 2 requires Node 24 and Vite 8, a higher floor than Solid 2.0 itself.
Diagnostics written for agents
Development builds now report reactive mistakes with a stable code, a source location and a fix. One example is STRICT_READ_UNTRACKED, which flags a reactive value read directly in an effect callback. The post frames this as help for both developers and coding agents, a topic our report on the Harvard paper on review bottlenecks with coding agents covers from the review side.
Tooling includes lint rules, Chrome Performance Tracks integration and an updated Sentry plugin. Chrome's own tooling for agents is covered in our report on Chrome DevTools MCP and its 63 tools.
What the announcement leaves out
The post contains no bundle sizes and no benchmark numbers, so any claim that 2.0 is faster or smaller than 1.x is unsupported by the announcement. It also gives no count of production apps. InfoQ says only that v2 of SolidStart already runs in production apps such as the OpenCode Console.
If you maintain a Solid 1.x application: read the removal table, check your Node version against 22.12, and wait for the migration guide before touching a production branch. If you are starting a new project, 2.0.1 is the tag to pin, because 2.0.0 shipped with the hydration hang.
Sources
More in Software
- 01Levien's Next-100 Rust GUIs Post Counts About 20 New Toolkits and Bets Against egui's Immediate ModeThe Linebender author credits AI rewrites for the surge; egui's own README concedes the trade-off he is pressing on.
- 02C++26 Is Reopened: The 13–9–12 Ballot, the Enforced Label That Answers It, and What Is Still OpenSutter's Búzios report says the committee kept contracts, added one paper, and will send C++26 to a second ballot with no published date.
- 03OpenAI Says Codex Cannot Run in Docker for iOS Builds, and Docker Launches It With Codex's Sandbox OffBolin's November 18 post lists Seatbelt, Bubblewrap and MXC as Codex's three sandboxes; Docker's page defaults to --dangerously-bypass-approvals-and-sandbox.
- 04CLI-Anything Has 62,119 Stars and a README With Three Different Test TotalsThe HKUDS project turns desktop software into agent-callable CLIs; its own per-harness lines sum to 158 more tests than it reports.