Build, verify and distribute
Use the developer build command to generate a complete Loom distribution directory:
Run intloom build without a path from the source directory. Pack dist, whose manifest is generated by Compiler; authors do not maintain generated entry exports. SDK and packages needed by emitted JS/declarations belong in dependencies or peers. Compiler and CLI are development dependencies.
Check Schemas, Code, Tools and key routes, then install the actual archive in an independent project to verify declarations, resources, interaction, persistence and recovery. Use the archive’s actual path:
Configure the project for your execution mode before running; see the CLI documentation. intloom loom manages built packages; intloom build addresses developer source.
The current Loom protocol is 2026-10-15, independently of npm package versions. Rebuilds use stable logical resource IDs, while recovery still checks actual artifact content. Retain packages required by unfinished Runs and do not replace resources while a Service uses them.
npm pack creates a local archive; publication is a separate operation. Compilation and controlled tests do not prove real-model quality or full business acceptance. See Compiler reference for errors, warnings and interruption handling.