NestJS developers face a common pain point: managing module imports, exports, and providers creates significant configuration overhead. A new framework called Rikta aims to solve this by removing modules entirely. Built on Fastify, it keeps NestJS's decorators and dependency injection but automates wiring. Services are discovered automatically, eliminating the manual array management that bogs down larger codebases.

Rikta scans for classes decorated with @Injectable() or @Controller(), building a global dependency graph at startup. This zero-config approach cuts development time for new features. The framework also integrates Zod for validation, allowing a single schema to provide both runtime checks and TypeScript types. Benchmarks show Rikta is 41% faster on GET requests than NestJS, with only 2-5% overhead over vanilla Fastify.

For teams, Rikta suits startups and small-to-medium projects where velocity is key. It's less ideal for large organizations requiring strict module boundaries or extensive NestJS ecosystem plugins. The trade-off is clear: less boilerplate versus explicit dependency documentation. As microservices grow, tools that reduce configuration friction while maintaining type safety will gain traction among developers seeking productivity without sacrificing structure.