@czap/compiler

Compiles boundary definitions — named states over numeric thresholds — and per-state values into @container CSS rules, GLSL/WGSL shader uniforms, ARIA attributes, and AI manifests.

You usually don't install this directly — it arrives as a dependency of @czap/vite, which compiles your authored CSS at build time. Install @czap/vite instead unless you want to call a compile target yourself, e.g. in your own build script.

Install

# inside a build integration (the usual path):
pnpm add @czap/vite # brings @czap/compiler with it

# to run the example below directly (pnpm does not hoist transitives):
pnpm add @czap/compiler @czap/core effect@beta

effect must be the Effect 4 beta — a bare pnpm add effect installs 3.x and fails the peer check.

30 seconds

import { Boundary } from '@czap/core';
import { CSSCompiler } from '@czap/compiler';

const width = Boundary.make({
  input: 'width',
  at: [[0, 'sm'], [768, 'lg']],
});

const result = CSSCompiler.compile(width, {
  sm: { 'font-size': '14px' },
  lg: { 'font-size': '18px' },
}, '.card');

console.log(result.raw);

Prints two @container blocks: (width < 768px) styling .card at 14px, and (width >= 768px) at 18px. result.containerRules holds the same output as structured data.

Where it sits

This is a layered package of pure functions from definitions to text — no DOM, no file system, nothing thrown. Its only @czap dependency is @czap/core, the source of the boundary, token, style, and theme definitions it compiles. Live evaluation as values change at runtime lives in @czap/quantizer; writing compiled CSS into your bundle is @czap/vite's job. See the package surfaces map for the full layout.

If it does nothing

State keys in the second argument are all optional, so a misspelled state name produces no rule and no error — the output is just missing a block. If result.raw is shorter than expected, compare your keys against boundary.states.

Docs

• Getting started
• Authoring model — what you type, what comes out
• Glossary — the vocabulary used above
• API reference — generated from source

Part of LiteShip — powered by the CZAP engine (Content-Zoned Adaptive Projection), distributed as @czap/* packages.