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

@vizij/arora-web-wasm

v0.1.2

Published

Run a Vizij runtime in the browser as an Arora device: wasm bindings over arora-web's BrowserRuntime.

Readme

@vizij/arora-web-wasm

Run a Vizij runtime in the browser as an Arora device.

The wasm module (built from crates/interop/vizij-arora-web) assembles an arora-web BrowserRuntime over the Vizij interop seams — a blackboard store, a rig HAL, and your node graph as the device's behavior. One device, one store, one step loop: the graph reads its input nodes' paths from the store each tick and writes its outputs back, and JS talks to the same store.

Use

import { init, startDevice } from "@vizij/arora-web-wasm";

await init();
const device = await startDevice(graphSpec); // a Vizij graph spec (object or JSON)

// each animation frame (dt in ms, e.g. from requestAnimationFrame timestamps):
device.setValue("sensor/x", { f32: 0.75 });
device.step(dtMs);
const changes = device.drainChanges(); // path -> ValueJSON | null

device.dispose();

Values cross the boundary in the normalized ValueJSON vocabulary from @vizij/value-json; setValue/writeValues accept its ValueInput shorthands.

Build

The pkg/ wasm artifacts are produced by wasm-pack from the repository root:

pnpm run build:wasm:arora-web   # wasm-pack build -> npm/@vizij/arora-web-wasm/pkg
pnpm --filter @vizij/arora-web-wasm run build