// the take
A decorator-driven Node.js API starter combining Express, routing-controllers, TypeORM, and TypeGraphQL, aimed at teams who want a Laravel-style structured backend with REST and GraphQL from day one. Good fit for someone who likes class-based controllers and dependency injection over a minimal Express app.
Wires routing-controllers, class-validator, and TypeORM together so you get request validation, DTO-based responses, and auto-generated Swagger docs from the same decorators instead of three separate configs. The GraphQL layer isn't an afterthought — it has DataLoader batching built into a custom @DLoader decorator, which is the part people usually get wrong when bolting GraphQL onto an existing REST app. Testing is split into real unit, integration (against SQLite), and e2e (supertest) layers rather than just unit tests with everything mocked.
No commits since May 2023, so it predates two and a half years of TypeORM, TypeGraphQL, and Node releases — expect peer dependency conflicts and CVEs in transitive packages if you try to npm install today. The whole architecture leans on reflect-metadata and experimentalDecorators, which is the TypeScript decorator model that's being phased out in favor of the TC39 standard — adopting this now means inheriting a migration problem later. Auth is barely sketched out: a single AuthService.ts plus an authorizationChecker, with real implementation pushed off to Auth0's docs rather than shown in the code. Running REST, GraphQL, TypeORM, TypeDI, and event-dispatch together is a lot of moving parts for a 'boilerplate' — if you only need REST or only need GraphQL, you're carrying the other half's complexity for nothing.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →