Build step added to internal compute package
A missing build step in the internal compute package caused Docker deployments to crash. A new compilation pipeline ensures TypeScript compiles to JavaScript for predictable production runtimes.
The internal compute package worked in local development but failed during Docker deployments. Without a dedicated build step, Node.js attempted to execute raw TypeScript files directly, which caused containers to crash at runtime. This update introduces a standard compilation pipeline, converting the TypeScript source into JavaScript before it reaches production.
By aligning the build process with the rest of the internal ecosystem, the @internal/compute package now behaves identically across local development machines and remote containers. Infrastructure teams can deploy the package knowing Node.js has the correctly compiled files to execute.
View Original GitHub Description
The @internal/compute package had its main/types pointing to ./src/index.ts with no build step. This works in dev (tsc resolves .ts at compile time) but fails at runtime in Docker because Node.js can't load .ts files directly.
Added tsconfig.build.json and build/clean/dev scripts matching the pattern used by schedule-engine and other internal packages. Exports now point to dist/.