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

@chestnutlabs/toolpath-core

v0.5.0

Published

Neutral ToolpathIR and capability model for the Chestnut Labs G-code Preview toolpath stack.

Readme

@chestnutlabs/toolpath-core

Neutral ToolpathIR and capability model for the Chestnut Labs G-code Preview toolpath stack. This is the replacement seam for the whole stack: the parser writes it, renderers and analyzers read it. See docs/design/DD-001.

Design rules

  • The canonical IR is plain, transferable data — a small header plus structure-of-arrays typed buffers (not object graphs). Positions are Float32 deltas relative to a Float64 originOffset (floating origin, DD-001 §4.6).
  • Unknown is a valid state. Optional/derived data carries a Confidence (known | inferred | approximated | unavailable); missing values are sentinels (NaN, 0), never fabricated data.
  • This package depends on nothing — no three, DOM, Vue, or AnyBridge (DD-002 boundary).

Contents (scaffold)

  • ir.tsToolpathIR, header, segments (SoA), layers/tools/objects, capabilities, MoveKind, FeatureRole, IR_SCHEMA_VERSION.
  • builder.tsToolpathIRBuilder (accumulate segments → canonical typed-array IR).
  • source-index.tsbuildSourceIndex / segmentAtByte (byte offset → segment; live-progress input).
  • bounds.ts — extrude-only and travel-inclusive bounds.
npm run build      -w @chestnutlabs/toolpath-core   # tsc -> dist
npm run typecheck  -w @chestnutlabs/toolpath-core
npm test           -w @chestnutlabs/toolpath-core

Status: scaffold (E1, issue #32). The builder accumulates into number arrays and converts to typed arrays in finalize(); E2's worker parser will write directly into growable typed buffers. Package extraction/publish is gated by DD-002 §7 and the release DD (E7/DD-008).