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

@superb-ai/image-kit

v0.4.0

Published

Paint — Rust/wgpu 2D annotation editor for the web (wasm). Generic, framework-agnostic web runtime over the `editor` domain + `paint_engine` renderer.

Readme

@superb-ai/image-kit

Rust/wgpu 2D annotation editor for the web (wasm). Generic, framework-agnostic web runtime over the editor domain + paint_engine renderer (this repo).

Use

import { init, create_web_editor, PaintEditor, Tool } from '@superb-ai/image-kit';

// Ergonomic:
const ed = await PaintEditor.mount(canvas);
ed.setTool(Tool.Box);
ed.start();

// Or drive the raw WebEditor yourself (build your own framework binding):
await init();
const web = await create_web_editor(canvas, devicePixelRatio);
web.set_tool('draw_box');
web.tick();

The raw WebEditor surface is in pkg/paint_image_kit_wasm.d.ts.

Building an editor with an AI agent? Point it at AGENT.md — the grimoire scroll: tool catalog, keymap, gestures, custom-tool (SAM) and read-back patterns, React lifecycle gotchas, all verified by e2e/.

Custom tools (e.g. SAM) — without forking the editor

A host builds an annotation via a draft: the editor owns the preview, snap, commit, and undo; your async work (e.g. a SAM inference call) stays in your code.

// 1. your tool's click → start a draft (class assigned upfront).
ed.beginDraft('polygon', 'car');
// 2. (your async SAM call — entirely in your code.)
const mask = await sam.segment(prompt);   // → flat xy image-space coords
// 3. inject the result. ringLens = vertices per ring (ring 0 = outer, 1.. = holes).
ed.draftSetPolygon(mask.coords, mask.ringLens);   // shows a live preview
// 4. accept → committed, undoable annotation; or ed.cancelDraft().
const id = ed.commitDraft();

The editor renders the draft preview in the wgpu canvas; SAM masks keep their holes / disjoint regions. The interaction (which click is a prompt, refine loops) is yours; the result polygon's editing is the editor's.

Reading back geometry — anchor HTML chrome over shapes

tick() renders shapes to the canvas (opaque). To put DOM UI (labels, tooltips, accept/reject buttons) over a shape, read its screen box — no need to re-render:

const box = ed.annotationScreenBounds(id);   // [x, y, w, h] logical px, or null
const hit = ed.hitTest(localX, localY, 5);    // topmost annotation uuid, or null

Build

npm run build       # wasm-pack --release → ./pkg  (what publish ships)
npm run build:dev   # faster, unoptimized

Requires the Rust toolchain + wasm-pack. pkg/ is a build artifact (git-ignored); prepublishOnly rebuilds it (--release) before every publish.

Publish

Versioned, like @superb-ai/prism:

npm version patch          # bump
npm publish                # builds --release via prepublishOnly, then publishes

See repo services/image-kit notes for the dev-account / token flow.