Introducing nextjs-nestapi
· 2 min read
Next.js App Router route handlers are fast and simple — and that simplicity starts to hurt once an API grows past a handful of endpoints. Every route is its own file, request parsing is manual, and there's no shared structure for organizing controllers, validating input, or documenting what you've built.
NestJS solves exactly this with controllers, decorators, and DTOs — but pulling in a full Nest runtime (modules, a DI container, its own HTTP adapter) inside a Next.js app is a lot of machinery for what is usually just "organize my API routes."
nextjs-nestapi is the middle ground.