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

@redwilly/canvaskitengine

v0.0.13

Published

This library is a browser vector engine rebuilt in TypeScript with CanvasKit as the rendering backend.

Readme

canvaskitengine

This library is a browser vector engine rebuilt in TypeScript with CanvasKit as the rendering backend.

Install:

bun install
bun run build

That build emits both:

  • dist/canvaskitengine.js
  • dist/canvaskit.wasm

Import the wasm asset directly

If you want explicit control over the wasm URL, the package also exports it as a subpath:

import wasmUrl from "canvaskitengine/canvaskit.wasm";
import { CanvasEngineInit } from "canvaskitengine";

await CanvasEngineInit({
  wasmUrl,
});

Direct CanvasKit usage

If you want to see the backend explicitly, bootstrap CanvasKit yourself and hand the runtime to the engine:

import { CanvasEngineInit, createCanvasKitRuntime } from "canvaskitengine";

const runtime = await createCanvasKitRuntime();

await CanvasEngineInit({ runtime });

const engine = document.createElement("canvas-engine");
document.body.appendChild(engine);

If you prefer, you can also pass locateFile directly instead of importing the wasm subpath.

You can also provide a preloaded CanvasKit instance directly:

import CanvasKitInit from "canvaskit-wasm";
import { CanvasEngineInit, CanvasKitRuntime } from "canvaskitengine";

const canvasKit = await CanvasKitInit({
  locateFile: (file) => `/dist/${file}`,
});

await CanvasEngineInit({
  runtime: new CanvasKitRuntime(canvasKit),
});

Automatic CanvasKit loading

CanvasEngineInit() can also load CanvasKit with an explicit wasm path when needed:

import { CanvasEngineInit } from "canvaskitengine";

await CanvasEngineInit({
  locateFile: (file) => `/dist/${file}`,
});

Architecture note

CanvasKit is intentionally isolated behind the runtime layer:

  • src/runtime/canvaskit.ts: official canvaskit-wasm bootstrap helpers
  • src/runtime/index.ts: CanvasKit surface/paint/path/shader bridge, native font/typeface use, pattern shaders, fill rules, and native picture recording
  • src/engine/index.ts: host component and engine bootstrapping

That keeps the document model and editing logic renderer-agnostic while still using CanvasKit for actual drawing.