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

@orrery-diagrams/runtime

v0.4.0

Published

The engine inlined into every Orrery SVG: camera, states, scenarios, drill-down, tours; window.Orrery.mount for pages.

Downloads

507

Readme

@orrery-diagrams/runtime

The engine inlined into every interactive Orrery SVG: camera, states, scenarios, drill-down, sequence stepping and tours. Opened directly, a rendered SVG is interactive with no page around it: click a component to step it through its states, click a closed group to open it, Enter or a double-click zooms, Escape steps back out, arrows select, s cycles scenarios, brackets step, digits switch views. For a page of your own, the same engine mounts on the SVG and reports what it does.

npm install @orrery-diagrams/runtime
import { RUNTIME_SOURCE } from "@orrery-diagrams/runtime";
import { renderDocument } from "@orrery-diagrams/core";

const svg = await renderDocument(model, engine, { runtime: RUNTIME_SOURCE }); // the engine travels inside the file

In a page, orrery embed writes the diagram, orrery.js (the engine, defining window.Orrery) and a sample page. The engine has no user interface of its own; the page builds its controls from the interface:

const orrery = Orrery.mount(svgElement, { size: { width: 1200, height: 700 } });
orrery.views; orrery.scenarios; orrery.states; orrery.groups();
orrery.showView("data"); orrery.open(["sessions"]); orrery.zoom("db"); orrery.back();
orrery.setScenario("db-fails", 1); orrery.next(); orrery.prev(); orrery.setState("api", "degraded");
orrery.play(); orrery.stop(); orrery.reset();
orrery.on("change", (snapshot) => { /* view, open groups, zoom, scenario step and note, every state and reason, selection, sequence message */ });
orrery.destroy();

RUNTIME_SOURCE is the bundled engine as a string, for embedding; the browser entry is the module itself. Every method is described in the source, src/browser/index.ts, and exercised by the test suite in a DOM.

MIT.