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

invariantcad

v0.2.0

Published

Comprehensive, type-safe CAD-as-code for TypeScript

Readme

InvariantCAD

CI Documentation License: Apache-2.0

Comprehensive, type-safe CAD-as-code for TypeScript.

InvariantCAD turns an immutable, versioned design document into mesh or exact B-Rep geometry. Designs stay independent of WebAssembly pointers and kernel-specific objects, so they remain serializable, testable, and suitable for deterministic builds.

Status: 0.2.0 is the current public foundation release. Parametric modeling, sketches, assemblies, configurations, topology-aware features, analysis, and interchange are usable today. Draft geometry and some complete exact topology-history guarantees require the separately built owned OCCT facade. Drawings, GD&T, sheet metal, mates, CAM, and CAE remain roadmap work.

Why InvariantCAD

  • Native TypeScript authoring with dimension-aware expressions
  • Immutable, versioned JSON design documents, validated when parsed or evaluated and checked against the grammar while authoring
  • Replaceable geometry kernels: Manifold mesh and OpenCascade B-Rep
  • Parametric sketches, primitives, features, transforms, and Booleans
  • Semantic topology queries and persistent face, edge, and vertex references
  • Parts, nested assemblies, configurations, materials, and deterministic BOMs
  • Measurements, physical mass properties, design-impact analysis, and hashes
  • STL, OBJ, STEP, and BREP export with explicit resource ownership
  • Node.js and browser support with real WebAssembly browser tests

Install

pnpm add invariantcad

InvariantCAD is ESM-only and requires Node.js 22.13 or newer. npm, Yarn, and Bun can install the package as well; pnpm is used for repository development.

Quick start

import { createEvaluator, design, mm, vec3 } from "invariantcad";

const cad = design("parametric-box");
const width = cad.parameter.length("width", mm(40), { min: mm(1) });

const body = cad.box("body", {
  size: vec3(width, mm(20), mm(5)),
  center: true,
});
cad.output("body", body);

async function evaluateParametricBox() {
  const evaluator = await createEvaluator();
  try {
    const result = await evaluator.evaluate(cad.build(), {
      parameters: { width: 60 },
      outputs: ["body"],
    });
    if (!result.ok) {
      throw new Error(
        result.diagnostics.map((item) => item.message).join("\n"),
      );
    }

    try {
      const output = result.value.output("body");
      return {
        volume: output.measure().volume,
        stlBytes: output.export("stl").byteLength,
      };
    } finally {
      result.value.dispose();
    }
  } finally {
    evaluator.dispose();
  }
}

export const parametricBoxSummary = await evaluateParametricBox();
console.log(parametricBoxSummary);

createEvaluator() with no arguments selects the bundled Manifold runtime. profile: "mesh-preview" checks that same mesh contract explicitly. “Stock OCCT” names the unmodified exact backend, not the evaluator default; select and preflight it with profile: "mechanical-exact". Every evaluated design and evaluator owns native resources, so use the finally boundaries shown above.

Geometry backends

| Backend | Representation | Best for | Exchange | | --- | --- | --- | --- | | Manifold | Watertight triangle mesh | Fast default modeling and STL/OBJ workflows | STL, ASCII STL, OBJ | | OpenCascade | Exact B-Rep | Analytic geometry, topology, STEP, and BREP workflows | STL, ASCII STL, OBJ, STEP, BREP |

Since 0.2.0: The strong deterministic STEP contract described below is implemented and release-gated in the npm package. It was not part of 0.1.1.

The bundled zero-override createOcctKernel() stock runtime advertises the optional versioned deterministic STEP contract KERNEL_STEP_EXPORT_PROTOCOL_VERSION === 1, separately from the weaker nativeExports availability list. Its AP214IS single-product bytes are stable for the same backend shape representation, export options, metadata, and exact runtime artifact. An output that OCCT writes as several STEP products, such as a disjoint union, returns weak native bytes from a plain export("step") and fails with EXPORT_UNSUPPORTED when STEP options are passed. This is not geometric canonicalization, a portable cache identity, or canonicalization of imported or third-party STEP files. See Import and export for metadata defaults, Unicode encoding, and the distinction between the returned-output ceiling and the synchronous native writer's peak allocation.

Supplying wasm, moduleFactory, or attestedRuntime deliberately removes that strong envelope until the exact writer artifact is separately qualified. Those runtimes retain their ordinary weak native STEP export.

Automatic defaults map only the document name and output/part identity fields; they do not pass through arbitrary document or part metadata, material identity, or the active configuration.

Use createEvaluator({ profile: "mechanical-exact" }) for the supported stock OCCT baseline. The mounting-plate quickstart shows complete default and exact lifecycles, including STEP export and the caller-owned-kernel failure path.

Pass an explicit kernel when custom OCCT loading, an owned runtime, or another backend is required. See the kernel guide for the complete capability and deployment differences.

Capability snapshot

InvariantCAD 0.2 includes:

  • Length, angle, scalar, vector, and density expressions with dependency checks
  • Boxes, cylinders/cones, spheres, sketches, extrudes, revolves, and transforms
  • Exact bounded lofts and line/arc path sweeps through OCCT
  • Union, subtraction, intersection, fillet, chamfer, shell, and offset, plus draft with the owned OCCT facade only
  • Constraint-based sketches with lines, arcs, circles, rectangles, and closed polylines; regularPolygon works since 0.2.0 and always threw in 0.1.1
  • Semantic topology set queries plus persistent topology evidence
  • Materials, parts, nested assemblies, configurations, suppression, and BOMs
  • Volume, area, center of mass, inertia, density-aware mass, and gyration analysis
  • Document migration, deterministic serialization, feature hashes, and impact reports

With the reference solver, a radius, diameter, or equalRadius constraint that changes a loop arc's radius, or a constraint that moves its center, does not move the adjacent line endpoints, so the loop opens and evaluation fails with SKETCH_NO_CLOSED_REGION; see arcs in constrained loops. Since 0.2.0, that diagnostic's details give the gap and the curves on either side of it.

The support matrix distinguishes authoring, Manifold, stock OCCT, and owned-facade support feature by feature.

CLI

invariantcad validate model.json
invariantcad inspect model.json --kernel occt
invariantcad bom model.json --output assembly
invariantcad export model.json --output body --to body.step

See the CLI reference for configuration and parameter overrides, output selection, formats, and exit behavior.

Documentation

Read the hosted documentation, or browse its versioned source under docs/:

Type declarations with their source JSDoc ship with the npm package for editor-level API documentation.

Architecture

TypeScript builder
      ↓
Versioned JSON design document
      ↓
Validated evaluator + sketch solver
      ↓
Manifold mesh kernel or OpenCascade B-Rep kernel
      ↓
Owned results → measurements, topology, BOM, mesh, and exchange files

The public document is kernel-neutral. Backend handles never enter serialized design state, and all native lifetime boundaries are explicit.

Development

pnpm install --frozen-lockfile
pnpm check
pnpm lint
pnpm test
pnpm release:check

release:check builds the package, runs the complete Node test suite, validates source correctness and format hygiene, locks every JavaScript export to its source, declaration, API report, and package target, installs the packed tarball into a clean consumer, measures checked coverage, executes all six kernel/model reference benchmarks, validates the Mintlify site and links, audits production and development dependencies, and executes the production browser bundle in Chromium.

pnpm release:check, pnpm docs:dev, pnpm docs:validate, and pnpm docs:links use the pinned Mint CLI, which supports Node.js 20.17 through 24 and exits on Node.js 25 and newer. Run them with Node.js 24, as CI and the release workflow do.

See CONTRIBUTING.md before submitting a change. Project support and decision-making are documented in SUPPORT.md and GOVERNANCE.md.

Security

Report vulnerabilities privately through GitHub Security Advisories. Do not open a public issue for an undisclosed vulnerability. See SECURITY.md for supported versions and the WASM/native-code threat boundary.

License

InvariantCAD is licensed under Apache-2.0. Its geometry backends have their own notices and redistribution obligations; see THIRD_PARTY_NOTICES.md.