Skip to content
A declarative, efficient, and flexible JavaScript library for building user interfaces.
Branch: master
Clone or download
Latest commit fcee604 Apr 19, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
assets Add logo/slogan Mar 23, 2019
documentation Updates to underlying renderer Apr 15, 2019
dom Updates to underlying renderer Apr 15, 2019
h Updates to underlying renderer Apr 15, 2019
src Updates to underlying renderer Apr 15, 2019
test Fix #19, limit Proxy wrap to Arrays and Plain Objects Apr 6, 2019
.gitignore update deps Mar 13, 2019
.travis.yml Updates to underlying renderer Apr 15, 2019
LICENSE open source repo Apr 25, 2018 Add note about Prettier Apr 19, 2019
package-lock.json Updates to underlying renderer Apr 15, 2019
rollup.config.js Updates to underlying renderer Apr 15, 2019

     The Deceptively Simple User Interface Library

Build Status Coverage Status NPM Version Join the community on Spectrum

Solid is yet another declarative Javascript library for creating user interfaces. It does not use a Virtual DOM. Instead it opts to compile it's templates down to real DOM nodes and wrap updates in fine grained computations. This way when your state updates only the code that depends on it runs.

Key Features

  • Real DOM with fine-grained updates (No Virtual DOM! No Dirty Checking Digest Loop!).
  • Declarative data
    • Simple composable primitives without the hidden rules.
    • Function Components with no need for lifecycle methods or specialized configuration objects.
  • Less than 10% slower vs optimized painfully imperative vanilla DOM code. See Solid on JS Framework Benchmark.
  • Tiny in size, 7.07 kB minified and gzipped with all dependencies.
  • Supports modern features like JSX Fragments, Portals, Suspense, and Asynchronous Rendering.
  • Webcomponent friendly
    • Implicit event delegation with Shadow DOM Retargeting
    • Shadow DOM Portals
    • Custom Element friendly Suspense flow

A Simple Component looks like:
const HelloMessage = ({name}) => (
    Hello {name}

createRoot(() =>
    .appendChild(<HelloMessage name="Taylor" />)


To use Solid with JSX (recommended) run:

> npm install solid-js babel-plugin-jsx-dom-expressions

You can also run Solid from the browser directly with your flavor of renderer found in the Solid Standalone package.

For example get started with Tagged Template Literal version in the browser by simply including a script tag on the page.

<script src=""></script>

Solid State

It all starts with State. State objects are immutable so to update you call their companion setter function. Through the use of proxies they give the control of an immutable interface and the performance of a mutable one. Note only Plain Objects and Arrays are deeply wrapped.

import { createState, onCleanup } from 'solid-js'

const CountingComponent = () => {
  const [state, setState] = createState({counter: 0});

  const interval = setInterval(() =>
    setState({counter: state.counter + 1})
  , 1000);

  onCleanup(() => clearInterval(interval));

  return <div>{(state.counter)}</div>;

You can also deep set:

const [state, setState] = createState({
  user: {
    firstName: 'John'
    lastName: 'Smith'

setState('user', {firstName: 'Jake', middleName: 'Reese'});

You can also use functions:

const [state, setState] = createState({counter: 0});
setState('counter', c => c + 1);

This takes the form similar to ImmutableJS setIn for leaving all mutation control at the top level state object. Keep in mind that setState when setting an object attempts to merge instead of replace.

But where the magic happens is with computations(effects and memos) which automatically track dependencies.

createEffect(() =>
    displayName: `${state.user.firstName} ${state.user.lastName}`

console.log(state.displayName); // Jake Smith

Whenever any dependency changes the State value will immediately update. JSX expressions can also be wrapped in effects so for something as trivial as a display name you could just inline the expression in the template and have it update automatically.

Solid State also exposes a reconcile method used with setState that does deep diffing to allow for automatic efficient interopt with immutable store technologies like Redux, Apollo, or RxJS.

const unsubscribe = store.subscribe(({ todos }) => (
  setState(reconcile('todos', todos)));
onCleanup(() => unsubscribe());

Solid Rendering

Solid's rendering is done by the DOM Expressions library. This library provides a generic optimized runtime for fine grained libraries like Solid with the opportunity to use a number of different Rendering APIs. The best option is to use JSX pre-compilation with Babel Plugin JSX DOM Expressions to give the smallest code size, cleanest syntax, and most performant code. The compiler converts JSX to native DOM element instructions and wraps expressions to be wrapped in our computations when indicated by in inner parens {( )}.

Prettier and some compile to JS libraries like CoffeeScript will strip Parenthesis causing issues with Solid's JSX. So unfortunately they are incompatible at this time.

To get setup add this babel plugin config to your .babelrc, webpack, or rollup config:

"plugins": ["jsx-dom-expressions"]

And include at the top of your files:

import { r } from 'solid-js/dom'

Alternatively in non-compiled environments you can use Tagged Template Literals Lit DOM Expressions or even HyperScript with Hyper DOM Expressions.

For convenience Solid exports interfaces to runtimes for these as:

import { h } from 'solid-js/h';
import { html } from 'solid-js/html'

Remember you still need to install the library separately for these to work.


Templates in Solid are just Pascal(Capital) cased functions. Their first argument is an props object and return real DOM nodes. Other than that nothing is special about them.

const Parent = () => (
    <Label greeting='Hello'>

const Label = ({greeting, children}) => (

Since the all nodes from JSX are actual DOM nodes the only responsibility of top level Templates/Components is appending to the DOM. Since change management is independent of code modularization, Solid Templates are sufficient as is to act as Components, or Solid fits easily into other Component structures like Web Components.

import { createState, createRoot } from 'solid-js'

class Component extends HTMLElement {
  constructor () {
    const [state, setState] = createState({});
    const [props, __setProps] = createState({});

    Object.assign(this, {state, setState, props, __setProps});

  connectedCallback() {
    !this.shadowRoot && this.attachShadow({mode: 'open'});

    createRoot(dispose => {
      this.dispose = dispose;

  diconnectedCallback() { this.dispose && this.dispose(); }

  attributeChangedCallback(attr, oldVal, newVal) {
    this.__setProps({[attr]: newVal});

class MyComponent extends Component {
  constuctor () {
    this.setState({greeting: 'World'});
  render() {
    return <div>Hello {(state.greeting)}</div>


This project started as trying to find a small performant library to work with Web Components, that had easy interopt with existing standards. It is very inspired by fine grain change detection libraries like Knockout.js and RxJS. The idea here is to ease users into the world of Observable programming by keeping it transparent and starting simple. Classically the Virtual DOM as seen in React for all it's advances has some signifigant trade offs:

  • The VDOM render while performant is still conceptually a constant re-render
    • It feels much more imperative as variable declarations and iterative methods for constructing the tree are constantly re-evaluating.
  • Reintroduced lifecycle function hell that break apart the declarative nature of the data. Ex. relying on blacklisting changes across the tree with shouldComponentUpdate.
  • Homogenous promise of Components and the overly simplistic local state in practice:
    • Imposes boundaries on components to solve performance concerns
    • Prices you into a very specific but not necessarily obvious structure
    • Only served to make it more ambiguous when emerging best practices lead to specialized component classification anyway
  • Abstracts debugging to the point a <div /> is not longer just a div
  • VDOM libraries still are based around having a specialized data objects.

So the driving questions here are:

  • If the data is going to be specialized anyway can we use Proxies to move the complexity into it rather than the rendering while keeping the appearance simple?
  • Can this free up existing constraints on how you modularize your view code?
  • Does this approach ultimately provide more adaptibility while reducing the API surface?
  • Is fine grained change detection fundamentally more performant than the Virtual DOM?

Admittedly it takes a strong reason to not go with the general consensus of best, and most supported libraries and frameworks. And React's Hooks API addresses the majority of what I once considered it's most untenable faults. But I believe there is a better way out there than how we do it today.

I cover this in more detail in my Bring Your Own Framework Blog Series(links below).



Related Projects

Past Articles


This project is still a work in progress. While Solid's change management is reaching stability (this repo), I am still refining the rendering APIs from the DOM Expressions.

You can’t perform that action at this time.