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

@d3-polytree/canvas

v0.4.0

Published

Base SVG canvas toolbox (Canvas, ElementRegistry, ElementBuilder, SVG export) for the d3-polytree v2 ecosystem

Readme

@d3-polytree/canvas

Base SVG canvas toolbox for the d3-polytree v2 ecosystem — the diagram-js–style foundation the viewer, interactive-viewer, and editor are built on. It owns the DOM surface (a <div>-wrapped <svg> with a root <g> layer), an id-assigning element registry, a small element builder, and a standalone SVG-string exporter. Everything is wired as a didi module so it composes into the engine without any framework glue.

▶ Live demo in Storybook.

Install

pnpm add @d3-polytree/canvas d3-selection

d3-selection is a peer dependency (D3 v7) — the canvas manipulates the DOM through it, so the host application supplies the exact D3 slice it already uses. eventemitter3 and ids are bundled dependencies.

What's inside

| Export | Kind | Role | | ----------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Canvas | class | The rendering surface: a container <div>, an <svg>, and a root <g>. Exposes container/SVG/transform/size accessors and emits canvas.init / canvas.resized / canvas.destroy on the injected event bus. | | ElementRegistry | class | Id assignment (via ids) and an owned element store keyed by id. | | ElementBuilder | class | Assigns an id to a definition and runs a builder callback that renders it. | | IdsIdGenerator, SequentialIdGenerator | class | Pluggable id strategies — random (default) vs. deterministic sequential (node_1, node_2, …). | | getSvgString | function | Serialize an <svg> to a standalone string with the applicable CSS inlined; transient data-pfd-transient attributes are stripped from the exported clone. | | TRANSIENT_ATTR | const | 'data-pfd-transient' — the generic transient-render marker (written by viewport culling, never exported). | | canvasModule | didi module | Descriptor wiring Canvas / ElementRegistry / ElementBuilder into an injector. |

Type exports: ElementBuildFn, IdGenerator, DiagramEventMap, ElementClassName, MouseKind.

Usage

Standalone

import EventEmitter from 'eventemitter3';
import { Canvas } from '@d3-polytree/canvas';

const bus = new EventEmitter();
const host = document.getElementById('app')!;
const canvas = new Canvas({ container: host, width: 800, height: 600 }, bus);

bus.emit('canvas.init'); // finish wiring the surface
const svg = canvas.getSVGStr(); // serialize (CSS inlined) for export/thumbnails

Deterministic ids for reproducible output

import { SequentialIdGenerator, ElementRegistry } from '@d3-polytree/canvas';

// Sequential ids make serialized SVG byte-for-byte reproducible — the basis for
// the golden-file / SSR pipeline in @d3-polytree/ssr.
const registry = new ElementRegistry(new SequentialIdGenerator());

As a didi module

import { canvasModule } from '@d3-polytree/canvas';
// compose canvasModule into a Diagram module list; downstream drawers resolve
// `canvas`, `elementRegistry`, and `elementBuilder` from the injector.

Where it fits

canvas sits at the bottom of the dependency graph:

canvas + pfdn-moddle -> core -> viewer -> interactive-viewer -> editor

Most users consume it transitively through @d3-polytree/core and a component; import it directly only when building a custom surface or a bespoke exporter.

Links

License

MIT © David Castillo