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

@huaqiu/ecad-renderer

v0.2.4

Published

Reusable KiCad POD renderer extracted from ECAD Viewer

Readme

@huaqiu/ecad-renderer

Browser rendering entrypoints for the PODs emitted by @huaqiu/kicad-sexpr-parser. This package bundles the ECAD Viewer canvas, WebGL, viewport, symbol, footprint, schematic, PCB, and stroke/CJK glyph implementations. It does not parse KiCad files and does not define another model layer.

import { renderSymbol, renderFootprint, renderSchematic, renderPcb } from "@huaqiu/ecad-renderer";

const result = await renderSymbol(symbolPod, { width: 320, height: 240 });
document.body.append(result.canvas);

All APIs accept the corresponding boardProto or schematicProto POD from the parser package. Supplying canvas renders into an existing canvas; otherwise a canvas is created. The generated CJK stroke glyph table is bundled in JavaScript, so rendering has no font CDN or network dependency. Standalone renders intentionally omit the KiCad drawing sheet and zoom-fit the supplied symbol, footprint, schematic, or PCB geometry.

Whole-project ZIP rendering

renderProjectFromZip renders a whole KiCad project from its ZIP — by URL, Response, Blob, or raw bytes — without the host having to unpack it:

import { renderProjectFromZip } from "@huaqiu/ecad-renderer";

const result = await renderProjectFromZip("https://example.com/design.zip", {
    container: document.getElementById("stage"),
});
// result.canvas is already in the stage; result.viewer is the SchematicViewer.

It unpacks the ZIP the same way the ECAD Viewer app does (jszip) and renders the root schematic — the sheet named after the .kicad_pro project file (e.g. AAA.kicad_proAAA.kicad_sch), falling back to the first schematic, then to the first .kicad_pcb when the project has no schematic. Pass kind: "schematic" or kind: "pcb" to force a document kind.

loadProjectZip(source) is the DOM-free, environment-agnostic lower level — it returns the unpacked .kicad_sch / .kicad_pcb sources and the detected root schematic without touching a canvas, so it also runs in Node:

import { loadProjectZip } from "@huaqiu/ecad-renderer/project";

const { files, rootSchematic } = await loadProjectZip(zipUrl);

The current ECAD Viewer renderer is canvas/WebGL based. createRendererWorker exports the stable request/response protocol and worker asset, while direct render methods remain the compatible browser path until the upstream renderer supports an OffscreenCanvas target.

Mini integration example

npm run example:mini builds examples/mini-integration/build. Serve that directory with any static-file server and open index.html. It parses and renders the checked-in LMV761MAX_NOPB.kicad_sym and LMV761MAX_NOPB.kicad_mod fixtures directly into canvases.