npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

browser-runtime-solid1

v0.0.13

Published

Solid 1 JSX/TSX compiler and renderer adapter for browser-module-runtime

Downloads

400

Readme

browser-runtime-solid1

Independent Solid 1.x plugin for Browser Module Runtime 0.0.13. The existing solid() adapter remains Solid 2.

Usage

import {createRuntime} from 'browser-module-runtime';
import {solid1} from 'browser-runtime-solid1';
const runtime=createRuntime({plugins:[solid1({version:'1.9.10'})]});
runtime.define('/Counter.jsx',`import {createSignal} from 'solid-js'; export default function Counter(){const [n,setN]=createSignal(0);return <button onClick={()=>setN(v=>v+1)}>{n()}</button>}`,{type:'solid1-jsx'});
await runtime.mount({module:'/Counter.jsx',target:'#app'});

For declarative syntax, use <script type="solid1-jsx" module="/Counter.jsx" scope="demo"> and <runtime-render scope="demo" module="/Counter.jsx">, then await runtime.html.process({scope:'demo'}).

Use solid1({source:'host'}) only with page import-map entries for solid-js, solid-js/web, solid-js/html, and solid-tag-1. Explicit version uses esm.sh URL pinning per runtime (does not modify the page import map). One Solid major per BMR runtime: using solid1() and solid() together is intentionally rejected.

The compiler imports [email protected] directly and uses its transform(source,{filename}) API. JSX and TSX types are solid1-jsx and solid1-tsx; explicit type is recommended. Component props update in place with full snapshot replacement; authored custom-element children project as props.children. Solid 1 solid-js/html uses dynamic code generation in some paths (strict CSP may require adjustments). SSR, hydration, named slots, and dynamic authored-light-DOM mutation are out of scope.