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-node

v0.2.0

Published

Node.js 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-node is the NeMo Flow package for Node.js applications. It gives JavaScript and TypeScript code access to the same execution scopes, middleware, plugins, lifecycle events, and observability model used by the Rust runtime.

The package is implemented as a napi-rs native extension, but Node.js users should install it from npm rather than depend on the Rust crate directly.

Why Use It?

  • 🧭 Own execution context in Node.js: Group agent, tool, and LLM work into one scope tree from JavaScript or TypeScript.
  • 🛡️ Put policy around callbacks: Register guardrails and intercepts for request rewriting, blocking, sanitization, and execution wrapping.
  • 📡 Emit one lifecycle stream: Send runtime events to in-process subscribers, Agent Trajectory Interchange Format (ATIF), OpenTelemetry, or OpenInference workflows.
  • 🧩 Use package entry points by need: Import the main runtime surface plus typed, plugin, adaptive, and observability helpers from npm.

What You Get

  • npm package for Node.js: A Node.js 20 or newer package backed by a napi-rs native extension.
  • Managed tool and LLM execution: Helpers that emit lifecycle events and run middleware in a consistent order.
  • Middleware APIs: Guardrails and intercepts for tool and LLM boundaries.
  • Observability exporters: Subscriber and exporter support for common runtime telemetry flows.
  • Additional entry points: nemo-flow-node/typed, nemo-flow-node/plugin, nemo-flow-node/adaptive, and nemo-flow-node/observability.

Installation

Install the npm package in a Node.js 20 or newer project:

npm install nemo-flow-node

Getting Started

Register a subscriber and emit a mark inside a scope:

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

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

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

  deregisterSubscriber("printer");
}

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

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

Documentation

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