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

@ybelik/scene-tracer

v0.1.0

Published

Image → traced SVG with a deterministic auto-tune ladder (the ybelik trace stage). Wraps wasm_vtracer; runs in browser and Node; writes settings-are-data sidecars from the CLI.

Readme

@ybelik/scene-tracer

Image → traced SVG, auto-tuned. The trace stage of the ybelik pipeline (generate → trace → compile → reveal — see the root README): a deterministic layer_difference ladder walks the trace until the path count lands in the jank-safe band, then the result is ready for @ybelik/scene-compiler.

The vector core is visioncortex vtracer via wasm_vtracer — CLI-parity verified on real photographic input (identical path count and render vs the native vtracer CLI). Succeeded the project's Python trace_scene.py on 2026-07-16.

CLI (Node)

npx @ybelik/scene-tracer image.png scene.svg
# or with a custom band / ceiling:
npx @ybelik/scene-tracer image.jpg scene.svg --min 1500 --max 3500 --max-kb 2048

Prints the chosen cell, the ladder it walked, and any flag; writes a scene.settings.json sidecar — the full reproduction recipe (settings-are-data). PNG and JPEG in; SVG (with viewBox) out.

Browser (ESM, no build step)

import * as glue from 'https://cdn.jsdelivr.net/npm/[email protected]/wasm_vtracer_bg.js';
import { initTracer } from 'https://cdn.jsdelivr.net/npm/@ybelik/[email protected]/scene-tracer.js';

const tracer = await initTracer({
  glue,
  wasm: 'https://cdn.jsdelivr.net/npm/[email protected]/wasm_vtracer_bg.wasm',
});
const { svg, settings } = tracer.traceScene(imageData.data, imageData.width, imageData.height);

The visitor's device pays the CPU (~1–3 s per ladder step at 1024 px); nothing uploads.

Policy

DEFAULT_POLICYcolor_precision: 8 (pinned) · ld_ladder: [8,16,24,32,48,64] · target_paths: [1500, 3500] · max_kb: 2048 · downscale_px: 1024. Override any key via traceScene(..., { policy }). Flags: band-edge · over-ceiling · chunky-by-content (features, not failures). The numbers' home — rationale and acceptance criteria: TRACE-SETTINGS.md.

MIT · part of the ybelik story engine.