Platform and DevOps teams who own the CI hot path
Faster CI test stages
Cut the test stage in your CI pipeline by serving warm runs from the rjest daemon instead of paying Jest startup on every job.
The problem
The test stage is often the longest step in CI, and most of its time is Jest startup — config parsing, transform setup, worker boot — repeated on every job and every retry.
How rjest helps
Keep jestd warm across steps in a job. Once the daemon is up and the transform cache is populated, subsequent test invocations in the same runner land in milliseconds instead of seconds.
What that looks like in practice
- ▸Warm the daemon in an early step; reuse it for all later test invocations in the job.
- ▸The blake3 transform cache can be persisted between runs as a CI cache artifact for faster cold starts.
- ▸Use --json to feed structured results straight into your CI reporting without ANSI scraping.
- ▸No change to jest.config — the same suite that runs on Jest runs on rjest.
Try it on this workflow
See the architecture, browse more use cases, or read the guides.