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

@azphalt/azdk

v0.1.1

Published

The typed API an azphalt extension is written against.

Readme

@azphalt/azdk

The typed surface an azphalt extension is written against. It turns the strings in the spec — capabilities, contributions, params, the UI schema — into a typed TypeScript API, so authors get types and autocomplete for the whole contract.

This package is types plus thin author helpers only. It has no runtime and reaches nothing on its own: the real Host is provided by a conforming runtime (see @azphalt/runtime-reference and @azphalt/runtime-wasm), which injects it and enforces the capability grants. Nothing here can touch a host engine, camera, sensors, the filesystem, or the network — see the never-list in spec/capability-model.md.

Writing an extension

Author a contribution with one of the define* helpers and export it under the name your manifest's contributes entry points at. The helper brands the function so a runtime can resolve it by kind.

import { defineFilter } from "@azphalt/azdk";

// manifest: contributes.filters = [{ id: "invert", name: "Invert", entry: "invert" }]
export const invert = defineFilter((ctx) => {
  const bmp = ctx.bitmap.read(ctx.target);      // ctx is capability-gated
  for (let i = 0; i < bmp.data.length; i += 4) {
    bmp.data[i] = 255 - bmp.data[i];
    bmp.data[i + 1] = 255 - bmp.data[i + 1];
    bmp.data[i + 2] = 255 - bmp.data[i + 2];
  }
  ctx.bitmap.write(ctx.target, bmp);
  ctx.canvas.requestRedraw();
});

defineFilter, defineTool, and defineCommand cover the three contribution kinds. The ctx a runtime passes in exposes only the sub-APIs whose capability the manifest declared and the host granted — an ungranted capability is absent, not an erroring stub.

What's in the box

  • Manifest & contributionsManifest, Kind, Runtime, Capability, AssetType, AssetContribution, Contributes, and the Filter/Tool/Command contribution shapes.
  • The host surfaceHost and its sub-APIs (CanvasApi, LayersApi, BitmapApi, SelectionApi, ColorApi, ParamsApi, AssetsApi), plus LayerRef.
  • PixelsBitmap (opt-in depth: 8-bit Uint8ClampedArray by default, 16-bit Uint16Array), RGBA, BitDepth, and the helpers bitDepth / bytesPerChannel / maxChannelValue.
  • UI schemaPanel and the control types (slider, number, toggle, select, color, text, button, group) hosts render natively (see spec/ui-schema.md).
  • Repository API typesRepositoryIndex, PackageSummary, PackageSearchResponse (see spec/repository-api.md).
  • Author helpersdefineFilter, defineTool, defineCommand, and FORMAT_VERSION.

Related