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

@orcish/dag

v1.0.0

Published

Immutable, type-safe directed acyclic graph (DAG) with a fluent class API and a tree-shakeable pure-function core: topological sort, cycle detection, and traversals.

Readme

@orcish/dag

An immutable, type-safe directed acyclic graph for TypeScript. Every structural operation returns a new graph — old snapshots never change — and acyclicity is enforced as you build: adding an edge that would close a cycle throws rather than corrupting the graph.

Ships two interchangeable APIs over the same data: a fluent Dag class and a tree-shakeable set of pure functions over an immutable DagRaw snapshot. No runtime dependencies; ESM-only; works in Node and the browser.

Install

pnpm add @orcish/dag

Usage

import { Dag } from '@orcish/dag';

// `idOf` maps each node value to its key. Nodes can be any type.
const dag = new Dag({ idOf: (n: { id: string }) => n.id })
  .addNode({ id: 'wake' })
  .addNode({ id: 'coffee' })
  .addNode({ id: 'code' })
  .addEdge('wake', 'coffee')
  .addEdge('coffee', 'code');

dag.topologicalSort(); // [{id:'wake'}, {id:'coffee'}, {id:'code'}]
dag.roots(); // [{id:'wake'}]
dag.leaves(); // [{id:'code'}]
dag.descendants('wake'); // [{id:'coffee'}, {id:'code'}]

// Each structural method returns a new instance — the original is untouched.
dag.addEdge('code', 'wake'); // throws CycleError; `dag` is unchanged

Two APIs, one model

The Dag class is a thin, fluent wrapper. If you prefer plain functions, the same operations are exported directly and operate on the immutable DagRaw snapshot:

import { addEdge, addNode, emptyDagRaw, topologicalSort } from '@orcish/dag';

let g = emptyDagRaw<{ id: string }>(n => n.id);
g = addNode(g, { id: 'a' });
g = addNode(g, { id: 'b' });
g = addEdge(g, 'a', 'b');
topologicalSort(g); // [{id:'a'}, {id:'b'}]

dag.toRaw() exposes that snapshot — the interop boundary for handing the graph to external tooling such as @orcish/dag-mermaid.

What's included

  • Constructionnew Dag({ idOf }), Dag.from(nodes, edges, { idOf }), and the pure emptyDagRaw / buildDag.
  • Mutation (all return a new graph) — addNode, addEdge, removeEdge.
  • QueriesgetNode, hasNode, hasEdge, size, nodes(), predecessors, successors, ancestors, descendants, inDegree, outDegree, roots, leaves.
  • AlgorithmstopologicalSort, topologicalGenerations, bfs, detectCycles, isDAG, wouldCreateCycle.

Invariants & errors

The graph keeps itself well-formed and signals violations by throwing:

  • DuplicateNodeError — adding a node whose id already exists.
  • UnknownNodeError — referencing a node that isn't in the graph.
  • SelfLoopError — an edge from a node to itself.
  • CycleError — an edge (or a buildDag input) that would create a cycle.

wouldCreateCycle(from, to) is the non-throwing pre-check if you'd rather test before adding.

License

MIT © Michael Martin