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

@solidrt/cli

v0.0.73

Published

Readme

@solidrt/cli

Developer tooling for SolidRT: sol, one command-line tool covering the whole cycle of a @solidrt/core application: scaffold, develop, inspect, ship. A GUI inspector, itself a SolidRT app, is in progress alongside it.

LLM agents: AGENTS.md in this package is a dense, self-contained quickstart.

Bun is a dev prerequisite only; apps run on the bundled flux runtime. Invoke via bun run sol <command>. A scaffolded project wires the common commands into scripts, so day-to-day work is bun run dev, bun run android (and server, client, pack for the rest).

Commands

| Command | | | --- | --- | | sol init <dir> | scaffold a new project into a new (empty) folder | | sol run [file] | dev server + local client window | | sol server [file] | dev server only | | sol client | client only, attached to the project's dev server | | sol android | install and launch the client on a connected Android device | | sol demo [n] | list the demos the CLI ships, or run one | | sol console | start the dev console: the dev servers on this machine and their clients | | sol check [file] | build and typecheck, writing nothing | | sol test [file] | run the tests (tests/*.test.ts) on the flux runtime | | sol bundle [file] | transpile to JS or bytecode (dist/bundle/) | | sol render [file] | render frames offscreen, optionally replaying a script | | sol pack [file] | bundle + compile to a standalone executable (experimental) | | sol mcp | MCP server (stdio) exposing the running dev server to agents |

sol --help lists every command and option; sol --version prints the version. Run from the project root to work on the project (its entry is solidrt.entry in package.json, default src/index.tsx); pass a file to work on that file on its own.

Develop

sol run

Starts the dev server and a local client window against it. The server pushes the bundle to every connected client, so one server can drive a desktop window and a phone at the same time; edits reach them on an explicit reload (the MCP reload tool) or on save.

Split them when you need to:

sol server                        # server only
sol client                        # client only, the project's server (from its root)
sol client --server 192.168.1.5:34884  # client only, pointed at that address
sol android                       # install and launch on a connected device

Inspect

sol mcp

Exposes the running app to a coding agent: logs, stats, the live render tree, screenshots, GPU resources, input injection, a virtual-time transport, reload, and the app's own debug commands. A scaffolded project ships an .mcp.json, so Claude Code attaches with no setup.

Record and replay

sol run --capture session.json
sol render --script session.json --fps 60 --duration 5

--capture records key events from connected clients to a script; render replays it headlessly and writes frames, which makes bug reports reproducible and turns an interaction into a video.

Ship

sol check .                # build and typecheck every entry, no build output
sol test                   # run every tests/*.test.ts on the flux runtime
sol bundle                 # transpile to JS or bytecode
sol pack                   # standalone executable (experimental)

sol bundle --flux and sol pack --flux target the bare Flux runtime instead of a SolidRT app, for scripts and servers with no UI.

Layout

One folder per command under src/, named for what it does; the first line of each says its runtime. src/server/ is the dev server, a flux script (bun-free at runtime, its own tsconfig); every other command runs on bun. src/lib/ is what the bun commands share, src/types/ the type-only contracts between the two runtimes. Each command folder carries its docs.md (this site); the depth agents need lives in agents/ at the package root, as in the other packages.