Transpile test sources once per run

Compile the TypeScript that test subprocesses load once, before the tests start.

Prompt

Evaluate and apply this CI technique to my repository: Transpile test sources once per run.

Compile the TypeScript that test subprocesses load once, before the tests start.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/compile-test-sources-once.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How OpenAI used this technique

Read what OpenAI changed and follow the original sources.

Transpile test sources once per run

The Node SDK's tests start hundreds of child processes. Each used to load a TypeScript compiler and transpile the same sources; the suite now compiles the example, CLI and SDK sources once per Vitest invocation and points the subprocesses at that snapshot.

Node 22 job for the whole pull request, which also enables Node's compilation cache, bounded concurrency for package downloads and type checks, and an invariant JSON parse hoisted out of a property-test loop: 5m37s to 3m47s (1m32s before the regression on main), one successful run per revision Source

Use it when: A test suite starts many subprocesses that each transpile the same sources.
Before applying it: The compiled snapshot belongs to one run; never restore it across runs.

How OpenAI used this technique

Transpile test sources once per run

Company Playbooks