[matej21]

Makes @contember/bindx-compiler publishable, so the next release ships it next to the runtime packages.

Why compiled JS

The runtime packages ship TypeScript source (exports: ./src/index.ts), which consumer bundlers compile. The compiler is different: a consumer imports it from vite.config.ts, and Node runs that config. Node does not strip types from files under node_modules, so importing .ts source from there fails.

Changes

• packages/bindx-compiler/package.json:
  • no longer private; version aligned with the other packages
  • exports/main/types point at dist/
  • build:js bundles src/index.ts with bun build --target=node --packages=external
  • @contember/bindx-react is a workspace:* peer, so bun pm pack pins it to the exact release version
• The root build (which the publish workflow runs) also runs build:js. Declarations still come from tsc --build.
• New README.md: installation, Vite setup, the runtime killswitch and validate mode, and numbers from a trial.

Trial on a large production app

• 614 chains and roots compiled, 23 bailed.
• The browser end-to-end suite gave the same pass and fail set with and without the compiler. In validate mode, no under-fetch warnings and no unfetched-field errors.
• The production build took about 60 % longer (20 s → 32 s). The bundle grew by 0.3 %.
• Page load times showed no measurable difference.

Verification

• bun run typecheck: clean.
• bun run test: 2523 pass. Compiler suite: 242 pass.
• Packed the package with bun pm pack and installed the tarball in an empty Node project. import { bindxCompiler } from '@contember/bindx-compiler' works, and the transform compiles a sample component.

Status

• Review: not reviewed separately (packaging only; the compiler itself was reviewed in feat: build-time selection compiler (experimental) #69).
• CI: pending.
• Before merge: green CI. After merge: tag a release.

🤖 Generated with Claude Code