Gauntlet: Node.js test runner with TypeScript compilation and minimal dependencies

Gauntlet is not a test framework in the traditional sense, but rather a lightweight orchestration layer. It addresses a specific frustration in the Node.js ecosystem: the bloated dependency trees associated with runners like Mocha and the increasingly brittle JIT compilation provided by ts-node. By acting as a wrapper around the built-in 'node:test' module, Gauntlet offloads the heavy lifting of execution to the Node.js runtime while handling the TypeScript compilation step upfront. Technically, the project's value lies in its approach to TypeScript. Rather than ignoring types for speed (as Vite does) or relying on slow, naive compiler calls, Gauntlet implements a cached language service. This allows it to maintain type safety between the library and the tests at build time without the performance penalty of full recompilation on every run. The compiled assets are mirrored into a hidden cache folder, ensuring relative imports remain intact while keeping the primary source directory clean. The trade-off here is breadth for depth. Gauntlet is intentionally narrow; it doesn't aim to replace the feature-richness of Jest or Mocha. It lacks a complex plugin ecosystem and accepts the current quirks of the 'node:test' event API. However, for an engineer who views a 50-deep dependency tree as a liability and wants a 'pytest-like' experience for TypeScript on Node, this is a surgical solution. Who should care? If you are building high-reliability ESM projects where dependency provenance is a security or stability concern, Gauntlet is a compelling alternative. It moves the project toward a 'standard library' approach to testing, reducing the surface area for future breaking changes caused by third-party maintainer churn.