InvariantCAD 0.1.0
InvariantCAD 0.1.0 is the first public foundation release of the comprehensive, type-safe CAD-as-code system for TypeScript.Highlights
- Immutable, canonical, versioned design documents with stable IDs and frozen v1-v6 compatibility.
- Dimension-safe parameters and expressions, sketches, constraints, profiles, parts, nested fixed assemblies, materials, configurations, and deterministic bills of materials.
- Robust mesh modeling through Manifold WebAssembly and exact B-Rep modeling through stock OpenCascade WebAssembly.
- Exact primitives, extrusion, revolution, Booleans, bounded ruled lofts, bounded line/arc sweeps, fillets, equal-distance chamfers, shells, whole-solid offsets, and optional owned-facade draft.
- STEP, text and binary BREP, STL, and OBJ exchange.
- Kernel-neutral volume, area, bounds, center of mass, inertia, principal-axis, radius-of-gyration, and density-aware physical-mass analysis.
- Semantic topology selectors and fail-closed persistent face, edge, and vertex references with explanation reports and a published torture corpus.
- Authored impact analysis, feature Merkle hashes, bounded artifact/cache protocols, conformance auditing, and canonical semantic observation.
- Structured diagnostics, explicit native ownership, a CLI, package-consumer smoke tests, and real Chromium coverage for both shipped WebAssembly kernels.
Install
pnpm add invariantcad Node.js 20.19 or newer is required. The package is ESM and supports modern browsers with explicit WebAssembly URLs when required by the bundler.Public entry points
- invariantcad
- invariantcad/conformance
- invariantcad/kernels/occt
Important boundaries
- No shipped kernel advertises a production cross-run shape codec yet, and the evaluator does not yet read or write cached shapes.
- The separately built InvariantCAD-owned OpenCascade facade is not included in the npm package and remains unpublished pending external review.
- Stock OpenCascade provides the base exact feature set. Complete exact topology evolution for selected advanced operations requires an explicitly supplied, matched owned-facade build.
- The standalone Manifold core runtime is pinned by npm integrity, identified upstream build provenance, and per-file SHA-256 inside the package. Embedded component notices ship with it, and its unrelated vulnerable image/glTF dependency tree is absent. Production releases require a zero-advisory audit across production and development dependencies.