Repository navigation
Boundra v0.1.2
Boundra v0.1.2
Release Summary
Boundra v0.1.2 strengthens the public preview after the first external CRUD dogfooding exposed gaps in installation, boundary enforcement, runtime errors, repetitive code, and performance measurement. The boundra npm package now supports both the runtime and native CLI flow, from project initialization through Vite development diagnostics.
Highlights
- Adds non-destructive workspace initialization through
pnpm exec boundra init. - Adds an npm CLI launcher that downloads the platform-specific Rust binary, verifies its SHA-256 checksum, and runs it from a versioned user cache.
- Adds BR-005 to block imports from
apps/**that bypass a domain public API and reach domain-internal paths. - Extends
BoundraRuntimeErrorwith field paths, provider-neutral validation issues, and a safetoJSON()representation. - Adds
boundra/viteto surface runtime contract and boundary errors in a development overlay. - Adds
createHttpTransportandgenerate resourceto reduce HTTP and CRUD contract boilerplate. - Adds 1,000/10,000-source-file benchmarks and a CI smoke gate to track CLI performance regressions.
Installation
Install on Node.js 20 or later:
pnpm add boundra@0.1.2 zod
pnpm exec boundra init --name my-app
pnpm exec boundra create-domain tasks
pnpm exec boundra generate resource tasks/task
pnpm exec boundra check-boundariesNative archives and Rust source installation remain supported:
cargo install --git https://github.com/qtaghdi/boundra --tag v0.1.2 boundra-cliBreaking Changes
None. This is an additive release compatible with the v0.1.1 runtime and existing route/query/mutation contract APIs.
Known Limitations
- On first npm CLI execution without a cache, GitHub Release access and Unix
taror Windows PowerShell are required. Controlled or offline environments can useBOUNDRA_CLI_PATH. - The Vite integration still performs a full boundary scan on each source update and does not yet use an incremental cache.
- Domain field schemas generated by
generate resourcestart as safe empty objects and must be completed by the application. createHttpTransportprovides the protocol client only; the server router adapter remains the responsibility of the application or framework integration.
Verification
- Node.js 20, 22, and 24 runtime CI
- Linux x64, macOS x64/arm64, Windows x64 CLI and npm launcher CI
- 59 Rust tests plus runtime, Vite integration, and generated example execution
- packed
boundra@0.1.2online/offline clean-room installation and TypeScript type checking - BR-001 through BR-005 boundary and domain graph verification
- 1,000-file benchmark CI gate and 10,000-file local baseline
- npm OIDC trusted publishing and GitHub Release SHA-256 artifact pipeline