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

@simten/ui

v0.13.0

Published

Canvas, editor, and waveform React components for Simten. Built on React Flow with dagre layout and Zustand stores.

Readme

@simten/ui

React components for the Simten circuit editor, canvas, and sandbox — the building blocks used to construct simten.dev's own editor UI.

This is the low-level UI kit. If you just want to embed a runnable circuit in a page, use @simten/embed instead — it wraps @simten/ui's primitives in a turn-key component.

Use @simten/ui directly when you need to build a custom editor, a non-standard canvas layout, or your own variant of the sandbox harness.

Install

npm install @simten/ui @simten/core react react-dom

What's in it

| Subpath | Purpose | |---|---| | @simten/ui/canvas | CircuitCanvas — the React Flow-based visual canvas | | @simten/ui/nodes | Node renderers for primitives (gates, registers, peripherals, …) | | @simten/ui/monaco | SimtenCodeEditor — Monaco with IntelliSense for circuit source (below) | | @simten/ui/editor | Simulator state capture/restore helpers | | @simten/ui/editor/stores | Zustand stores backing the editor | | @simten/ui/editor/components | ClockControls, CircuitTabBar, CircuitSelector, SignalOutputPanel | | @simten/ui/waveform | WaveformViewer for VCD playback | | @simten/ui/sandbox | Cross-origin sandbox primitives for running untrusted circuit code | | @simten/ui/share | Encode/decode share links |

Each subpath has its own entry point with full TypeScript types — pick the smallest set you need.

Looking for useCircuitSimulator? It lives in @simten/embed, alongside builtFromIR.

The code editor

@simten/ui/monaco gives you Monaco pre-wired for circuit source: typed completions and hovers for the Simten stdlib, plus automatic type acquisition so third-party imports (react, zod, …) resolve to real types.

pnpm add @simten/ui @monaco-editor/react
import { SimtenCodeEditor } from '@simten/ui/monaco';

<SimtenCodeEditor value={source} onChange={setSource} />;

If you already own a Monaco instance — a collaborative editor with a Yjs binding, say — use the headless primitives instead and keep your own <Editor>:

import { setupSimtenIntellisense, useTypeAcquisition } from '@simten/ui/monaco';

useTypeAcquisition(source, monaco);

<Editor path="file:///circuit.ts" beforeMount={setupSimtenIntellisense} onMount={bindYjs} />;

The model needs a real file:/// URI: TypeScript resolves modules by walking up from the containing file looking for node_modules, and Monaco's default inmemory:// scheme has nothing to walk. SimtenCodeEditor sets this for you. Get it wrong and every import silently resolves to any.

This subpath handles types only. Circuit source executes in the sandbox iframe, which resolves imports from esm.sh independently — so code can run fine while its types are still downloading. That's why module-not-found diagnostics are suppressed while semantic validation stays on.

Type acquisition fetches from jsDelivr at runtime. Pass typeAcquisition={{ enabled: false }} to opt out, or { typescriptCdn } to self-host; failures degrade to "no completions", never a broken editor.

Peer dependencies

  • React 18 or 19
  • @simten/core
  • @monaco-editor/reactoptional, required only by @simten/ui/monaco

Monaco is an optional peer, so it is never installed unless you ask for it: every other subpath stays Monaco-free on disk and in your bundle. That also means it isn't auto-installed, hence naming it explicitly in the install command above. You won't import @monaco-editor/react yourself — SimtenCodeEditor does — and monaco-editor follows automatically as a peer of it.

Monaco itself is not bundled by anyone here: @monaco-editor/react loads it from a CDN at runtime, and the monaco-editor package is present for its types.

Docs

Component API and integration examples at https://simten.dev/docs. Source: https://github.com/simtenHQ/simten.

License

Apache-2.0