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

nemo-flow-wasm

v0.2.0

Published

WebAssembly bindings for the NeMo Flow agent runtime.

Readme

License GitHub Release Codecov PyPI npm node npm wasm Crates.io Crates.io Crates.io Ask DeepWiki

NeMo Flow

nemo-flow-wasm is the NeMo Flow WebAssembly package for JavaScript environments that load the runtime through WebAssembly. It exposes the same execution scope, middleware, plugin, lifecycle event, and observability concepts as the Rust runtime.

The Rust crate in this directory is build machinery for the generated npm package. JavaScript users should install the npm package rather than depend on the Rust crate directly.

This surface is experimental and source-first. Use the repository source tree and WebAssembly tests when validating behavior, and prefer Rust, Python, or Node.js for primary documented application integrations.

Observability support is also experimental. The WebAssembly target does not support grpc OTLP transport, and file-backed observability plugin sinks require a host runtime with filesystem access.

Why Use It?

  • 🌐 Bring NeMo Flow to WebAssembly: Use the shared runtime model from JavaScript environments that load the package through WebAssembly.
  • 🧭 Keep execution context visible: Group scope, tool, LLM, middleware, and subscriber behavior into the same runtime event tree.
  • 🛡️ Register JavaScript policy callbacks: Apply guardrails and intercepts around managed tool and LLM execution.
  • 📦 Consume it as npm: Install the generated package instead of depending on the Rust crate directly.

What You Get

  • WebAssembly runtime bindings: Access to NeMo Flow scope, tool, LLM, middleware, subscriber, plugin, typed, and adaptive APIs.
  • Managed tool and LLM execution: Helpers that emit lifecycle events for JavaScript-managed callbacks.
  • Middleware registration: Guardrail and intercept APIs for JavaScript callbacks.
  • Additional entry points: nemo-flow-wasm/typed, nemo-flow-wasm/plugin, nemo-flow-wasm/adaptive, and nemo-flow-wasm/observability.
  • Generated npm package: A wasm-pack build prepared for JavaScript package consumption.

Installation

Install the npm package in a JavaScript project:

npm install nemo-flow-wasm

For local source validation from the repository root:

npm run build:pkg --workspace=nemo-flow-wasm
npm run test:pkg --workspace=nemo-flow-wasm

Getting Started

Register a subscriber and emit a mark inside a scope:

const {
  ScopeType,
  deregisterSubscriber,
  event,
  registerSubscriber,
  withScope,
} = require("nemo-flow-wasm");

async function main() {
  registerSubscriber("printer", (runtimeEvent) => {
    console.log(`${runtimeEvent.kind} ${runtimeEvent.name}`);
  });

  await withScope("demo-agent", ScopeType.Agent, async (handle) => {
    event("initialized", handle, { binding: "wasm" }, null);
  });

  deregisterSubscriber("printer");
}

main().catch((error) => {
  console.error(error);
  process.exitCode = 1;
});

The main runtime API is exported from nemo-flow-wasm. Additional entry points are available at nemo-flow-wasm/typed, nemo-flow-wasm/plugin, nemo-flow-wasm/adaptive, and nemo-flow-wasm/observability.

Documentation

NeMo Flow Documentation: https://nvidia.github.io/NeMo-Flow