Build

How to build, deploy, and publish in this monorepo.

Local Build

npm run build                              # Build all packages (core deps first)
npm run build -w packages/<name>           # Build a specific package
npm run build -w workspaces/<name>         # Build a specific workspace
npm run build:core-deps                    # Build types, errors, fabric (dependency order)
npm run clean                              # Remove all dist/ directories

Build order matters: types -> errors -> fabric -> everything else. The top-level npm run build handles this automatically via build:core-deps.

Typecheck and Lint

npm run typecheck                          # Typecheck all workspaces
npm run typecheck -w packages/<name>       # Typecheck a specific package
npm run lint                               # Lint everything (quiet mode)
npm run format                             # Auto-fix lint + sort package.json

CI/CD Workflows

NPM Check (npm-check.yml)

Runs on pushes to feature branches. Validates code quality before merge.

Jobs (all parallel):

• Lint: Node 24, npm run lint
• Typecheck: Node 24, npm run typecheck (continue-on-error)
• Unit Test: Matrix [Node 22, 24, 25], npm test with optional Datadog tracing
• LLM Client Test: Conditional, only when packages/llm/** changes

NPM Deploy (npm-deploy.yml)

Publishes packages to npm. Skips already-published versions automatically.

Stack Deployments

CDK infrastructure deploys via separate workflows:

Branching Strategy

Tags

Publishing Packages

Packages publish automatically when merged to main. The workflow:

1. Iterates over all packages/*/
2. Skips private: true packages
3. Compares local version to npm registry
4. Publishes only if version is new (with --provenance)

To publish a pre-release:

1. Bump version to include -rc.0 or -dev.0 suffix
2. Run npm i --package-lock-only
3. Push a tag: git tag rc-description && git push origin rc-description

Completion Criteria

See .claude/skills/green/SKILL.md.