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

proper-pixel-art-ts

v0.0.3

Published

Node-first TypeScript port of KennethJAllen/proper-pixel-art.

Readme

proper-pixel-art-ts

Node-first TypeScript port of KennethJAllen/proper-pixel-art.

Current baseline tracks upstream commit 93945ff.

Goals

  • mirror upstream module structure: utils, colors, mesh, pixelate
  • keep browser-first APIs over ImageData
  • support OpenCV.js through injection or script loading
  • support Node package consumption first
  • preserve upstream behavior before adding extra features

Current scope

  • upstream-style mesh detection and cell sampling pipeline
  • transparency handling and dominant-color logic
  • PIL-aligned MAXCOVERAGE palette built in TS, plus pluggable quantizer override
  • OpenCV loader helper that auto-detects Node vs browser
  • Vitest coverage for colors, mesh helpers, and pixelate/downsample flow

Remaining work

  • fixture parity against the full upstream asset set
  • packaging polish and CI

Current caveat

The Node package builds, imports, initializes OpenCV, and passes unit tests, but it does not yet match the upstream Python fixture outputs exactly. Use it as an active port, not as a verified drop-in equivalent.

Development

bun install
bun run build
bun run test
bun run test:parity

test:parity is the browser/OpenCV fixture suite. It requires a working Playwright Chromium install.

Example

import { loadOpenCv, pixelate } from 'proper-pixel-art-ts';

const cv = await loadOpenCv();
const result = await pixelate(inputImageData, {
  cv,
  initialUpscaleFactor: 2,
  numColors: undefined,
  transparentBackground: true,
});

In Node, loadOpenCv() falls back to loadOpenCvNode(), which initializes the runtime via @opencvjs/node (listed as an optional dependency — install it only if you need the Node loader).

Using from React / Vite / webpack

The package ships an exports map with browser and node conditions, so modern bundlers pick the right entry automatically. In a React app, the default import resolves to the pre-bundled browser ESM (dist/browser.js, ~32 KB):

import { loadOpenCv, pixelate } from 'proper-pixel-art-ts';
import { useEffect, useState } from 'react';

export function Pixelator({ source }: { source: HTMLImageElement }) {
  const [output, setOutput] = useState<ImageData | null>(null);

  useEffect(() => {
    let cancelled = false;
    (async () => {
      const cv = await loadOpenCv(); // injects <script src="https://docs.opencv.org/4.x/opencv.js"> on first call
      const canvas = document.createElement('canvas');
      canvas.width = source.naturalWidth;
      canvas.height = source.naturalHeight;
      canvas.getContext('2d')!.drawImage(source, 0, 0);
      const input = canvas.getContext('2d')!.getImageData(0, 0, canvas.width, canvas.height);
      const result = await pixelate(input, { cv, numColors: 16, scaleResult: 4, transparentBackground: true });
      if (!cancelled) setOutput(result);
    })();
    return () => { cancelled = true; };
  }, [source]);

  // …render `output` to a canvas
}

If you'd rather host OpenCV.js yourself, pass scriptUrl:

const cv = await loadOpenCv({ scriptUrl: '/static/opencv-4.10.0.js' });

Or skip the loader entirely and hand pixelate a cv namespace you've already initialized.

Entry points

| Subpath | Resolves to | Use when | |---|---|---| | proper-pixel-art-ts (browser bundler) | dist/browser.js | React, Vite, webpack, esbuild, rollup — picked via the browser export condition | | proper-pixel-art-ts (Node) | dist/node.js | Node scripts, SSR, tests — picked via the node export condition | | proper-pixel-art-ts/browser | dist/browser.js | Force the pre-bundled ESM regardless of bundler condition | | proper-pixel-art-ts/node | dist/node.js | Force the Node entry regardless of bundler condition |