Website • API Docs • Tutorial • Discord
You're on the
nextbranch — Solid 2.0. The public API differs from 1.x: split-phasecreateEffect, microtask batching,Loading/Erroredboundaries, draft-first store setters, async-in-computations, removedsolid-js/webandsolid-js/storesubpaths, and more.
- Migrating from 1.x? Start with
documentation/solid-2.0/MIGRATION.md.- Quick API reference:
packages/solid/CHEATSHEET.md(one screen, every public export).- Design rationale: the 2.0 RFCs at
documentation/solid-2.0/.- JSX compiler and DOM runtime live here (
@solidjs/babel-plugin,@solidjs/compiler,@solidjs/web). File those issues on this repo, not DOM Expressions.- Stable Solid 1.x? Use the default
mainbranch.
Solid is a declarative JavaScript library for building user interfaces. Instead of a Virtual DOM, it compiles templates to real DOM nodes and updates them with fine-grained reactivity. Declare your state and use it throughout your app — when a piece of state changes, only the code that depends on it re-runs.
import { createSignal } from "solid-js";
import { render } from "@solidjs/web";
function Counter() {
const [count, setCount] = createSignal(0);
const doubled = () => count() * 2;
// The component body runs once. Only `{doubled()}` updates when count changes.
return <button onClick={() => setCount(c => c + 1)}>{doubled()}</button>;
}
render(() => <Counter />, document.getElementById("app")!);Try it in our Playground.
Explain this!
Solid compiles your JSX to real DOM operations at build time. The component function runs once on mount; reactivity is per-expression, not per-render. The {doubled()} expression compiles to a tracked update that only touches that one DOM position when count() changes.
import { template, delegateEvents, insert } from "@solidjs/web";
import { createSignal } from "solid-js";
const _tmpl$ = /*#__PURE__*/ template(`<button>`);
function Counter() {
const [count, setCount] = createSignal(0);
const doubled = () => count() * 2;
return (() => {
const _el$ = _tmpl$();
_el$._$$click = () => setCount(c => c + 1);
insert(_el$, doubled);
return _el$;
})();
}
delegateEvents(["click"]);Reads update on the next microtask (or call flush() for synchronous interop). Effects are split into a tracking compute phase and a side-effecting apply phase — see MIGRATION.md for the full model.
- Fine-grained updates to the real DOM — no virtual DOM diff.
- Declarative reactive primitives (
createSignal,createMemo,createStore). - Render-once components — your component function is plain JavaScript that runs once.
- Automatic dependency tracking — reading reactive state subscribes to it.
- Microtask-batched updates with
flush()for synchronous interop. - First-class async: any computation can return a
Promise/AsyncIterable;<Loading>is the boundary. - Optimistic UI primitives (
createOptimistic,createOptimisticStore) and structuredaction(...)mutations. - Streaming SSR and progressive hydration.
- TypeScript-first, JSX-first, web-component friendly.
- Universal: write custom renderers via
@solidjs/universalto target non-DOM platforms.
npm i solid-js @solidjs/web
npm i -D @solidjs/babel-pluginAdd @solidjs/babel-plugin to your Babel config (or use Vite's Solid plugin) and configure TypeScript:
{
"compilerOptions": {
"jsx": "preserve",
"jsxImportSource": "@solidjs/web"
}
}For web projects, jsxImportSource points at @solidjs/web. In 2.0, solid-js owns renderer-neutral component types, while renderer packages such as @solidjs/web and @solidjs/h own their JSX namespaces and jsx-runtime type entries.
2.0 starter templates are tracked at solidjs/templates. Existing 1.x templates target 1.x.
The public API differs from any Solid examples that predate 2.0. Before generating Solid 2.0 code, read:
packages/solid/skills/solid-2.0/SKILL.md— the primer: the three rules that matter most, the 1.x → 2.0 corrections, and the primitives to reach for, in under 8 KB.packages/solid/CHEATSHEET.md— one-page reference; the bottom enumerates patterns that changed from 1.x.documentation/solid-2.0/MIGRATION.md— full migration guide.- docs.solidjs.com — the Solid 2.0 docs, with
/llms.txtand/llms-full.txt.
The primer and the cheatsheet ship inside the solid-js npm package (node_modules/solid-js/skills/solid-2.0/SKILL.md, node_modules/solid-js/CHEATSHEET.md; the build also emits the cheatsheet as the solid-2.0-cheatsheet skill). The packages carry the tanstack-intent keyword, so skill registries that scan node_modules find them.
This is a PNPM workspaces monorepo. The packages here version together as one fixed group:
| Package | Path | Purpose |
|---|---|---|
solid-js |
packages/solid |
Core runtime — components, flow controls, context, hydration. |
@solidjs/signals |
packages/signals |
Reactive primitives — signals, memos, effects, stores. |
@solidjs/web |
packages/web |
Web platform runtime — render, hydrate, SSR, Portal, dynamic. |
@solidjs/h |
packages/h |
Hyperscript / JSX factory. |
@solidjs/html |
packages/html |
Build-less tagged template literals. |
@solidjs/universal |
packages/universal |
Universal runtime for custom renderers. |
@solidjs/element |
packages/element |
Web Components wrapper. |
@solidjs/compiler |
packages/compiler |
Native Oxc JSX compiler. |
@solidjs/babel-plugin |
packages/babel-plugin |
Babel plugin for JSX compilation. |
Runtime DOM operations live in @solidjs/web (and @solidjs/universal / @solidjs/h / @solidjs/html).
Engineered for performance with years of research behind it — Solid's runtime cost is close to optimized vanilla JavaScript on the JS Framework Benchmark. Small, fully tree-shakable, fast on the server too. (Read more about Solid's performance.)
Performant state management is built in (Context, Stores, Projections). Async is a first-class capability of computations — no separate createResource model — with <Loading> / <Errored> boundaries and isPending for revalidation indicators. Full SSR, streaming, and progressive hydration when you're ready to move to the server.
Components are plain functions. Rendering is determined by how state is used — no rendering system to learn. Read-write segregation is encouraged but not enforced.
Built on JSX and TypeScript, integrates with the Vite ecosystem. Bare-metal abstractions give you direct access to the DOM. Growing ecosystem of primitives, component libraries, and build-time utilities.
SolidJS Core supports the last 2 years of modern Firefox, Safari, Chrome, and Edge (desktop and mobile). IE and similar sunset browsers are not supported. For server environments, Node LTS, the latest Deno, and Cloudflare Worker runtimes are supported.
Come chat on Discord. Solid's creator and the rest of the core team are active there, and we're always looking for contributions.
Support us with a donation and help us continue our activities. [Contribute]
Become a sponsor and get your logo on our README on GitHub with a link to your site. [Become a sponsor]