Sourcemap Explorer
Stack · npm package

solid-js

A declarative JavaScript library for building user interfaces.

latest 1.9.14· MIT· 524 versions publishedView on npm

About

A declarative JavaScript library for building user interfaces.

solidsolidjsuireactivecomponentscompilerperformance

What detecting solid-js tells you about a site

solid-js reveals a team that wanted React's JSX ergonomics without the virtual DOM — Solid compiles components to fine-grained reactive updates, so its presence signals a deliberate bet on runtime performance. It is still a minority choice, so finding it marks a team tracking the leading edge of front-end frameworks.

Why the exact solid-js version matters

Solid's reactivity primitives and the SolidStart meta-framework matured across the 1.x line; the exact version tells you which signal/store API the code targets and how settled the surrounding tooling is.

solid-js in a real-world stack

When you find solid-js in a bundle, it rarely travels alone. @solidjs/router and SolidStart for full apps; very few peripheral libraries, since Solid's primitives cover a lot.

Quick facts

Latest version1.9.14
LicenseMIT
AuthorRyan Carniato
Homepagesolidjs.com
Installnpm install solid-js
Direct dependencies3

What solid-js pulls in

solid-js declares 3 direct dependencies — each one also rides into any bundle that ships solid-js, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .

csstypeserovalseroval-plugins

How Sourcemap Explorer detects solid-js

solid-js ships as v1.9.14, published 2026-07-01 and carries 3 direct dependencies, 524 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when solid-js rides inside a deployed bundle — here is how the detection works.

We catch solid-js from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/solid-js/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.

  1. 1

    Confirm the site exposes sourcemaps

    In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `solid-js` paths live.

  2. 2

    Find the package in the bundle

    Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/solid-js/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/solid-js/package.json` gives you the exact installed version.

  3. 3

    Read the version directly from package.json

    Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/solid-js/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Major releases of solid-js

When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the solid-js version a site actually ships against the ecosystem.

Major
First release
Date
v1
1.0.0
2021-06-28
v0
0.0.1
2018-04-25

Recent security advisories for solid-js

The 1 most recent advisories affecting some versions of solid-js, aggregated from OSV.dev (GitHub Advisory + CVE data). A listing here doesn't mean the version a given site ships is affected — each advisory applies to a specific version range. Sourcemap Explorer reads the exact bundled version so you can check it against these ranges.

  1. HIGHCVE-2025-27109· 2025-02-25

    Solid Lacks Escaping of HTML in JSX Fragments allows for Cross-Site Scripting (XSS)

Recent versions

Version
Released
1.9.14
2026-07-01
1.9.13
2026-05-15
1.9.12
2026-03-24
1.9.11
2026-01-23
1.9.10
2025-10-27
1.9.9
2025-08-12
1.9.8
2025-08-06
1.9.7
2025-05-16

solid-js README

Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.

SolidJS

Build Status Coverage Status

NPM Version Discord Subreddit subscribers

WebsiteAPI DocsFeatures TutorialPlaygroundDiscord

Solid is a declarative JavaScript library for creating user interfaces. Instead of using a Virtual DOM, it compiles its templates to real DOM nodes and updates them with fine-grained reactions. Declare your state and use it throughout your app, and when a piece of state changes, only the code that depends on it will rerun.

At a Glance

import { createSignal } from "solid-js";
import { render } from "solid-js/web";

function Counter() {
  const [count, setCount] = createSignal(0);
  const doubleCount = () => count() * 2;
  
  console.log("The body of the function runs once...");

  return (
    <>
      <button onClick={() => setCount(c => c + 1)}>
        {doubleCount()}
      </button>
    </>
  );
}

render(Counter, document.getElementById("app")!);

Try this code in our playground!

Explain this!
import { createSignal } from "solid-js";
import { render } from "solid-js/web";

// A component is just a function that returns a DOM node
function Counter() {
  // Create a piece of reactive state, giving us an accessor, count(), and a setter, setCount()
  const [count, setCount] = createSignal(0);
  
  //To create derived state, just wrap an expression in a function
  const doubleCount = () => count() * 2;
  
  console.log("The body of the function runs once...");

  // JSX allows you to write HTML within your JavaScript function and include dynamic expressions using the { } syntax
  // The only part of this that will ever rerender is the doubleCount() text.
  return (
    <>
      <button onClick={() => setCount(c => c + 1)}>
        Increment: {doubleCount()}
      </button>
    </>
  );
}

// The render function mounts a component onto your page
render(Counter, document.getElementById("app")!);

Solid compiles your JSX down to efficient real DOM updates. It uses the same reactive primitives (createSignal) at runtime but making sure there's as little rerendering as possible. Here's what that looks like in this example:

import { template as _$template } from "solid-js/web";
import { delegateEvents as _$delegateEvents } from "solid-js/web";
import { insert as _$insert } from "solid-js/web";
//The compiler pulls out any static HTML
const _tmpl$ = /*#__PURE__*/_$template(`<button>Increment: `);

import { createSignal, createEffect } from "solid-js";
import { render } from "solid-js/web";

function Counter() {
  const [count, setCount] = createSignal(0);
  
  const doubleCount = () => count() * 2;
  
  console.log("The body of the function runs once...");
  
  return (() => {
    //_el$ is a real DOM node!
    const _el$ = _tmpl$();
    _el$.$$click = () => setCount(c => c + 1);
     //This inserts the count as a child of the button in a way that allows count to update without rerendering the whole button
    _$insert(_el$, doubleCount);
    return _el$;
  })();
}
render(Counter, document.getElementById("app"));
_$delegateEvents(["click"]);

Key Features

  • Fine-grained updates to the real DOM
  • Declarative data: model your state as a system with reactive primitives
  • Render-once mental model: your components are regular JavaScript functions that run once to set up your view
  • Automatic dependency tracking: accessing your reactive state subscribes to it
  • Small and fast
  • Simple: learn a few powerful concepts that can be reused, combined, and built on top of
  • Provides modern framework features like JSX, fragments, Context, Portals, Suspense, streaming SSR, progressive hydration, Error Boundaries and concurrent rendering.
  • Naturally debuggable: A <div> is a real div, so you can use your browser's devtools to inspect the rendering
  • Web component friendly and can author custom elements
  • Isomorphic: render your components on the client and the server
  • Universal: write custom renderers to use Solid anywhere
  • A growing community and ecosystem with active core team support
Quick Start

You can get started with a simple app by running the following in your terminal:

> npx degit solidjs/templates/js my-app
> cd my-app
> npm i # or yarn or pnpm
> npm run dev # or yarn or pnpm

Or for TypeScript:

> npx degit solidjs/templates/ts my-app
> cd my-app
> npm i # or yarn or pnpm
> npm run dev # or yarn or pnpm

This will create a minimal, client-rendered application powered by Vite.

Or you can install the dependencies in your own setup. To use Solid with JSX (recommended), run:

> npm i -D babel-preset-solid
> npm i solid-js

The easiest way to get set up is to add babel-preset-solid to your .babelrc, babel config for webpack, or rollup configuration:

"presets": ["solid"]

For TypeScript to work, remember to set your .tsconfig to handle Solid's JSX:

"compilerOptions": {
  "jsx": "preserve",
  "jsxImportSource": "solid-js",
}

Why Solid?

Performant

Meticulously engineered for performance and with half a decade of research behind it, Solid's performance is almost indistinguishable from optimized vanilla JavaScript (See Solid on the JS Framework Benchmark). Solid is small and completely tree-shakable, and fast when rendering on the server, too. Whether you're writing a fully client-rendered SPA or a server-rendered app, your users see it faster than ever. (Read more about Solid's performance from the library's creator.)

Powerful

Solid is fully-featured with everything you can expect from a modern framework. Performant state management is built-in with Context and Stores: you don't have to reach for a third party library to manage global state (if you don't want to). With Resources, you can use data loaded from the server like any other piece of state and build a responsive UI for it thanks to Suspense and concurrent rendering. And when you're ready to move to the server, Solid has full SSR and serverless support, with streaming and progressive hydration to get to interactive as quickly as possible. (Check out our full interactive features walkthrough.)

Pragmatic

Do more with less: use simple, composable primitives without hidden rules and gotchas. In Solid, components are just functions - rendering is determined purely by how your state is used - so you're free to organize your code how you like and you don't have to learn a new rendering system. Solid encourages patterns like declarative code and read-write segregation that help keep your project maintainable, but isn't opinionated enough to get in your way.

Productive

Solid is built on established tools like JSX and TypeScript and integrates with the Vite ecosystem. Solid's bare-metal, minimal abstractions give you direct access to the DOM, making it easy to use your favorite native JavaScript libraries like D3. And the Solid ecosystem is growing fast, with custom primitives, component libraries, and build-time utilities that let you write Solid code in new ways.

More

Check out our official documentation or browse some examples

Browser Support

SolidJS Core is committed to supporting the last 2 years of modern browsers including Firefox, Safari, Chrome and Edge (for desktop and mobile devices). We do not support IE or similar sunset browsers. For server environments, we support Node LTS and the latest Deno and Cloudflare Worker runtimes.

Testing Powered By SauceLabs

Community

Come chat with us on Discord! Solid's creator and the rest of the core team are active there, and we're always looking for contributions.

Contributors

Open Collective

Support us with a donation and help us continue our activities. [Contribute]

Sponsors

Become a sponsor and get your logo on our README on GitHub with a link to your site. [Become a sponsor]

FAQ

What is solid-js used for?

A declarative JavaScript library for building user interfaces.

How can I tell if a website is using solid-js?

Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `solid-js` from two complementary signals: `node_modules/solid-js/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.

How do I find out which version of solid-js a website is running?

Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `solid-js/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/solid-js/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 1.9.14, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.

What is the latest version of solid-js?

1.9.14, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.

Is solid-js actively maintained?

Very actively maintained — the last release shipped within the past three months. The last published release was 2026-07-01. Source code: https://github.com/solidjs/solid.

Does solid-js have known security vulnerabilities?

1 recent advisory affecting some versions of solid-js is listed in the "Recent security advisories" section above, aggregated from OSV.dev (GitHub Advisory + CVE data). Whether a particular site is exposed depends entirely on the exact version it ships — each advisory applies to a specific version range, not to the package as a whole. That is why the precise bundled version matters: Sourcemap Explorer reads the version a site actually runs, so you can check it against the affected ranges instead of assuming the latest release is what's deployed.

Where can I read more?

Project homepage: https://solidjs.com. Source code: https://github.com/solidjs/solid. Published on npm: https://www.npmjs.com/package/solid-js. Licensed as MIT.

Keep reading on Sourcemap Explorer

Detected by Sourcemap Explorer

When a bundle ships sourcemaps, we read the embedded package.json for solid-js and report the precise version (the registry's latest is v1.9.14, published 2026-07-01; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.

Install free on Chrome