Teams maintaining large TypeScript monorepos
Large TypeScript monorepos
In big TS monorepos the transform step dominates. rjest compiles with SWC natively and caches by blake3 hash so unchanged files never re-compile.
The problem
In large TypeScript codebases, Babel or ts-jest transform cost dominates test time, and that cost is re-paid every run because Jest has no persistent transform cache.
How rjest helps
rjest transforms TS and JSX with SWC in Rust and stores the output in a blake3-keyed sled cache. Only files whose bytes changed re-compile — across runs and across daemon restarts.
What that looks like in practice
- ▸SWC-native transforms replace the Babel/ts-jest chain.
- ▸Content-addressed cache means unchanged modules are never recompiled.
- ▸Cache survives daemon restarts and reboots.
- ▸Scales with change set, not with repo size.
Try it on this workflow
See the architecture, browse more use cases, or read the guides.