SolidJS 2.0: Async Signals, Smaller API, and AI Diagnostics SolidJS 2.0 reached stable on November 16, 2026, after 23 release candidates over 14 weeks, making async functions first-class in the reactive graph so that createMemo accepts async functions directly and the removed createResource is no longer needed. The release removes seven primitives including createResource, batch, startTransition, on, produce, createComputed and createMutable, retires the SolidStart meta-framework with no migration path, and grows the runtime from roughly 4.8 KB to 20.3 KB brotli, most of it the async signals scheduler. The release lands days after the TC39 Signals proposal reached Stage 4 for the ECMAScript 2026 specification, with expected gains of 2–3x performance over library-based reactivity. 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