SolidJS 2.0 hit stable on November 16, 2026 — five years after 1.0, and after 23 release candidates over 14 weeks. The headline feature is that async is now a first-class citizen inside the reactive graph, not an afterthought bolted onto the side. But the deeper story is timing: this ships days after the TC39 Signals proposal reached Stage 4, and after Angular, Vue, and Svelte all converged on the same primitives Solid pioneered. The revolution Ryan Carniato started — when most of the industry was still debating whether React Hooks were a good idea — is now the industry consensus.
Async Is Now Inside the Graph
In Solid 1.x, handling async data meant reaching for createResource and wrapping everything in <Suspense>. In 2.0, createMemo accepts async functions directly. The reactive graph handles suspension and resumption automatically — no race condition management, no loading state wiring, no useEffect chains.
// Solid 1.x
const [data] = createResource(() => fetchUser(userId()));
// Solid 2.0
const data = createMemo(() => fetchUser(userId()));
That two-line diff is the entire point. The framework absorbs the complexity so you don’t have to. <Suspense> is renamed to <Loading> and now handles only initial render — ongoing state changes are tracked via isPending without tearing down the UI. For synchronous access when you need it, latest(signal) and flush() give you escape hatches.
Seven Primitives Removed
The team cut createResource, batch, startTransition, on, produce, createComputed, and createMutable from the API surface. All seven were either subsumed into core behavior or replaced by cleaner alternatives.
batch is now automatic at the microtask level. startTransition is handled via loading boundaries. Store mutations use mutable proxy syntax instead of createMutable:
// Before
setState("todos", id, "done", true);
// After
setState(x => { x.todos[id].done = true });
Other renames worth noting: <SuspenseList> is now <Reveal>, onMount became onSettled, and classList is gone — class now accepts objects, arrays, and strings directly. The API got smaller and more consistent. That matters for AI-assisted development too: Solid 2.0 ships with diagnostics specifically tuned to catch the untracked reactive reads that trip up LLM-generated code.
SolidStart Is Gone
SolidStart, the official meta-framework, was retired with no migration path. This is the part of the release notes that will give many teams pause. The new approach is assembly: core Solid 2.0 primitives plus framework-agnostic Vite plugins, TanStack Query for data fetching, and whatever else fits your stack. It’s more flexible, but “assemble your own meta-framework” is a real cost that shouldn’t be glossed over.
If your team was running SolidStart in production, treat this as a forced migration, not an upgrade.
The Signals Revolution, Now Official
The TC39 Signals proposal reached Stage 4 this month, meaning native Signal.State and Signal.Computed are heading into the ECMAScript 2026 specification. The expected gains are significant: 2–3x performance over library-based reactivity and better memory management via browser-native C++ dependency tracking.
Meanwhile, the entire framework landscape has converged: Angular made signals the recommended state path, Vue absorbed the alien-signals algorithm, Svelte 5 runes are signals with different syntax, and Preact ships them first-party. Solid didn’t win the framework war — it won the ideas war, five years early.
The Bundle Size Trade-off
One honest data point before the verdict: Solid 2.0 is not as lightweight as 1.x. The runtime grew from roughly 4.8 KB (brotli) to 20.3 KB — most of it the async signals scheduler. It’s still lean compared to the full React ecosystem footprint, but the “ultra-lightweight” talking point needs updating. If you’ve been pitching Solid as the tiny framework option, factor this in.
Who Should Switch Now
If you’re building a new project and your team has appetite for a framework with a smaller ecosystem and no official meta-framework, Solid 2.0 is worth serious consideration. The async story is genuinely better than React’s, the reactivity model eliminates entire categories of stale-closure bugs, and the API is now cleaner than it’s ever been.
If you’re on SolidJS 1.x with SolidStart, plan the migration carefully — it’s manageable, but every async boundary in your codebase will need attention. For teams on React with no current pain points, there’s no urgent reason to switch. Watch the TC39 signals rollout and revisit when native reactivity lands in browsers.
The official migration guide is in the SolidJS repository. Full release notes and Ryan Carniato’s framing are in The Long Hold post on the SolidJS blog. For a React developer comparison, this breakdown on Morello Dev covers the practical differences in depth.

