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

@nanobpm/nano-bernd

v0.2.0

Published

Bernd — Nano BPMN's embedded engine. A universal FFI wrapper around the Nano engine compiled to wasm32. Zero runtime dependencies, no wasm-bindgen — a plain WebAssembly.instantiate host that works in Node, Deno, and browsers, and mirrors the same C-ABI th

Readme

@nanobpm/nano-bernd

Embedded Nano BPMN engine for Node, Deno and the browser. Codename Bernd — see ADR 0005.

Runs nano_engine.wasm (ABI v2) in-process — no server, no network, no native binaries. Same engine, same lifecycle model as the nanobpm-gateway-rest-server binary, just embedded.

Signature

      _   _                       ____                     _
     | \ | | __ _ _ __   ___     | __ )  ___ _ __ _ __  __| |
     |  \| |/ _` | '_ \ / _ \    |  _ \ / _ \ '__| '_ \/ _` |
     | |\  | (_| | | | | (_) |   | |_) |  __/ |  | | | | (_| |
     |_| \_|\__,_|_| |_|\___/    |____/ \___|_|  |_| |_|\__,_|

     Named for Bernd Ruecker, whose talks on decoupled workers,
     Sagas and the compensation pattern are the intellectual source
     of the embedded-engine design realised here.
     Artists sign their work. See ADR 0015.

Usage (Node/Deno)

import { EmbeddedEngine } from '@nanobpm/nano-bernd';

const engine = await EmbeddedEngine.create();
try {
  engine.deploy(bpmnXml);
  const { processInstanceKey } = engine.createInstance('order-fulfilment');

  for (const job of engine.activateJobs({ type: 'charge-card', worker: 'worker-1', maxJobs: 10, timeoutMs: 30_000 })) {
    // ...do work...
    engine.completeJob(job.key);
  }
} finally {
  engine.close();
}

Usage (browser)

The default create() uses node:fs to load the packaged wasm. In the browser, pass your own wasmBytes + manifest:

const [wasm, manifest] = await Promise.all([
  fetch('/nano_engine.wasm').then((r) => r.arrayBuffer()),
  fetch('/manifest.json').then((r) => r.json()),
]);
const engine = await EmbeddedEngine.create({ wasmBytes: wasm, manifest });

EmbeddedEngine.CODENAME === 'Bernd'.