Subscribe
0%
Illustration for: Solid 2.0 is stable: async built into reactivity, server functions in core, SolidStart retired. What breaks

Solid 2.0 is stable: async built into reactivity, server functions in core, SolidStart retired. What breaks

SolidJS shipped 2.0.0 on November 17, five years after 1.0. Async now lives inside the reactive graph, server functions are part of core, and dev builds give AI-agent-friendly diagnostics. It also removes createResource, batch, produce and other 1.x APIs, so libraries with open-ended peer ranges need checking before you upgrade.

Listen to this article0:00 / 4:52
solidjs/solid

A declarative, efficient, and flexible JavaScript library for building user interfaces

Language
TypeScript
License
MIT
Stars
36.3K
Try it
npm create solid@latest
View on GitHub

Solid 2.0 is out. The solidjs/solid repo tagged solid-js@2.0.0 on November 17. The npm registry shows 2.0.0 published at 05:19 UTC that day and now tagged latest, so a plain npm install solid-js gets the new major version. The release post, "The Long Hold", is dated November 16. It describes a release that builds async into the reactive graph, moves server functions into core and trims the API.

Why it matters: 2.0 is the first major version of the fine-grained reactive library in roughly five years, per the team. It is also a breaking release. Anyone who upgrades with a loose version range, directly or through a dependency, will hit removed APIs.

What's new

  • Async in the graph. Computations can return Promises or async iterators, and everything downstream handles them. <Loading> replaces <Suspense>, and isPending() reports background refreshes without pulling the current UI. Per the post, speculative state rolls back automatically.
  • Server functions in core. There are request/response RPC calls, plus live() for persistent streams over Server-Sent Events.
  • Diagnostics written for agents. Dev builds flag reactive mistakes with stable codes such as STRICT_READ_UNTRACKED, along with source locations and fix guidance. They also warn about waterfalls, effect loops and graph shapes that scale badly. Each code links to docs and to a repair guide shipped inside node_modules. A Sentry plugin brings the same checks to production.
  • Experimental syntax. The release adds support for ReactiveScript and TSRX.
  • SolidStart is retired. The team says core plus framework-agnostic Vite plugins now cover what the meta-framework did. It points to TanStack Query and Router as examples of the ecosystem filling the gap.

The team says it shipped 23 release candidates over 14 weeks, merging 971 pull requests and closing 753 issues. Its bar for stable was a full week with no regressions in ordinary app code and no crashes or hangs.

What breaks

The release post lists these APIs as removed: createResource, batch, startTransition, on, produce, createComputed and createMutable. Write-ups from the beta and RC period add renames that 1.x code will run into. The table below comes from a DEV Community guide written during the beta, so check it against the 2.0 docs before relying on it.

Solid 1.x Solid 2.0 (per beta-era guide)
createResource(fetcher) createMemo(() => fetch…) inside <Loading>
<Suspense> / <SuspenseList> <Loading> / <Reveal>
onMount onSettled
<Index> <For keyed={false}>
solid-js/web @solidjs/web
mergeProps / splitProps merge / omit
classList class accepting strings, objects or arrays
<Ctx.Provider value> <Ctx value>

Two behaviour changes deserve care. Writes are batched: a signal read straight after a set can return the old value until flush() runs, or you use latest(). createEffect is split into a tracked dependency function and an untracked apply function. InfoQ reported pushback on both during the beta. One GitHub commenter called the split effect API "cumbersome" and worried that deferred reads break the 1.x mental model. Creator Ryan Carniato replied that both are needed for consistent async.

Who should do what

  • New projects: npm create solid@latest starts on 2.0. The post points to the 2.0 docs and tutorial. It doesn't include a step-by-step migration guide.
  • Existing apps: Pin solid-js@^1 until you've audited the removed APIs. A 1.x line is still published under the v1-latest npm tag (1.9.19 at the time of writing).
  • Library authors: Check your peer ranges. On November 18 a bugsee issue flagged that its Solid SDK declares solid-js >=1.6, which lets apps resolve to an untested major version. The fix it suggests is to add 2.0 support or cap the range at <2.
  • SolidStart users: SolidStart is being retired as a separate framework. Plan for the Vite-plugin approach the team describes, or another router/framework stack.

The repo is MIT-licensed TypeScript with about 36,300 stars, according to GitHub's API on November 18. Watch how quickly the router, testing library and UI kits ship 2.0-compatible releases. That, more than the core, will decide when upgrading is practical.

Sources

  1. SolidJS — Solid 2.0: The Long Hold solidjs.com
  2. GitHub — solidjs/solid release solid-js@2.0.0 github.com
  3. InfoQ — SolidJS 2.0 Beta: First-Class Async, Reworked Suspense and Deterministic Batching infoq.com
  4. DEV Community — What is new in solid-js@2.0? dev.to
  5. npm registry — solid-js package metadata registry.npmjs.org
  6. GitHub — bugsee/bugsee-javascript issue #213: Solid 2.0.0 GA vs open peer range github.com

#SolidJS#Solid 2.0#JavaScript#TypeScript#frontend#reactivity#SolidStart#open source