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

@bysages/workflow

v0.3.1

Published

AI-ready workflow graphs for By Sages Elements — a headless graph protocol dressed in the paper-and-ink system, rendered by a swappable canvas engine

Readme

@bysages/workflow

npm version npm downloads npm license

The workflow canvas for By Sages Elements — a headless graph protocol (store, change stream, versioned serialization) with an AntV X6 adapter on top, dressed entirely by the paper-and-ink styles from @bysages/core.

Features

  • 🧠 Headless first — the protocol layer (types, store, serialize) imports no X6: executors, persistence, and tests run in Node, and the canvas engine stays replaceable
  • 🖋 Visuals live in core — cards, handles, edges, and the minimap are data-scope="workflow" styles driven by tokens; light/dark, accent, contrast, and density tiers come free
  • 🧩 Host-owned nodes — renderNode hands every node card to your framework (Vue, React, or plain DOM); the canvas never mounts content of its own
  • 🎛 Editor-grade defaults — drag, connect with direction-aware handles, rubberband select, undo/redo, delete, minimap, fit view; the elkjs auto layout reads the edges' ports and sweeps the way the graph flows
  • ⛓ Execution stays out of history — state writes (node:state, edge:state) ride a separate change source and never enter the undo stack

Installation

# pnpm
pnpm add @bysages/workflow

# npm
npm install @bysages/workflow

# yarn
yarn add @bysages/workflow

# bun
bun add @bysages/workflow

X6 is browser-only — import the canvas from client code only (a dynamic import in SSR apps).

Quick Start

Describe the graph as data, mount a canvas, and hand each card to your framework:

import { createWorkflowCanvas, createWorkflowStore } from "@bysages/workflow";

const store = createWorkflowStore({
  nodes: [
    {
      id: "start",
      type: "start",
      position: { x: 60, y: 40 },
      ports: [{ id: "out-1", dir: "out" }],
      data: { label: "Start" },
    },
    // …
  ],
  edges: [],
});

const canvas = createWorkflowCanvas(host, store, {
  // Your framework mounts the content of every node card.
  renderNode: (card, node) => {
    card.textContent = String(node.data.label ?? node.id);
  },
  minimap: { container: mapHost },
});

// Execution writes states back through the store — the canvas lights up.
store.setNodeState("start", "running");

// Persist the whole graph with a version envelope.
const saved = serializeWorkflowGraph(store.getGraph());

Every write goes through the store and fans out as a change; the canvas applies host changes, and host listeners observe canvas changes — drag a node and your store subscription sees it, write a position and the canvas moves it.

License