@intloom/compiler

Build Loom source packages into distributable ESM, TypeScript declarations, source maps and Skill assets. Compiler uses the contracts in @intloom/loom-sdk; it never executes business modules, creates Agents or depends on Kernel.

Build a Loom

With IntLoom installed, run intloom build [path]. Omit the path to build the current directory. The source package contains package.json.loom, tsconfig.build.json, and referenced Stage YAML, Code, Schema, Tool, Agent and Skill files. Keep each Stage's resources together; references are relative to the declaring file.

For programmatic builds:

import { compileLoom } from "@intloom/compiler";

const result = await compileLoom({ packageRoot: process.cwd() });
console.log(result.outputPath, result.diagnostics);

Requires Node.js 26.4.0+. Repository development uses Bun. Compiler is a development dependency; SDK and packages referenced by shipped JavaScript or declarations belong in dependencies or peers.

| Option | Purpose | | --- | --- | | packageRoot | Required source package directory | | tsconfigFile | In-package configuration; defaults to tsconfig.build.json | | logger | Optional caller-owned Utils logger |

compileLoom returns Promise<CompileResult> with source/output paths, package name/version, Loom name and warning diagnostics. Errors are LoomError values with located diagnostics in cause.diagnostics.

The generated dist is a complete package. Its manifest exports loom.generated.js, its declarations and ./package.json; the source manifest's export map is not copied. Pack dist, not the authoring directory. The entry exports exactly blueprint, codes and agentSpecs.

Compilation follows the entry's module dependencies, ignoring inherited TypeScript include and project references. It enforces SDK contract checks, validates routing and local re-export chains, checks JavaScript/declaration dependencies and copies referenced Skill directories. Unreachable Stages/Steps produce warnings; cycles are legal. Code/Agent IDs are stable for logical resource bindings. Identical inputs with the same compiler, dependencies and configuration produce repeatable output; stable IDs do not authorize recovery across changed executable content.

A package lock serializes builds. Generated source stays in .intloom-build-*; validation completes before replacing dist. Failed validation preserves the old output. A cleanup failure may occur after replacement. An interrupted .intloom-build.lock records its owner: verify the process has exited and inspect temporary previous-dist backups before removing the lock. Locks are never automatically stolen.

See Create a Loom, Compiler reference, build and distribute, source responsibilities and tests.