// the take
Ts.ED is a decorator-based TypeScript framework for Node.js that sits on top of Express or Koa. It takes the same NestJS-style approach — controllers, DI, pipes, interceptors — but with its own take on JSON Schema integration and platform abstraction. Aimed at teams who want structured, class-oriented API development without committing to NestJS's opinions.
OpenAPI docs are generated directly from your controller decorators and model classes via JSON Schema — no separate spec file to maintain, and it actually stays in sync. Platform abstraction is real: the same application code runs on Express, Koa, serverless (AWS Lambda), or as a CLI tool by swapping a config option. Bun.js runtime support is included, which most comparable frameworks haven't shipped yet. The DI system supports lazy loading and factory providers, so you're not stuck with constructor-only injection for complex initialization.
The README's own controller example has a bug — deleteUser references an undefined variable `user` instead of `id`, which doesn't inspire confidence in documentation quality. NestJS has 10–20x more stars, a vastly larger ecosystem of plugins and community modules, and is what most TypeScript Node.js devs already know; you'll be fighting that gravity on any team hire or Stack Overflow search. The framework leans heavily on legacy TypeScript parameter decorators and reflect-metadata, which puts it on the wrong side of the TC39 decorator spec transition — this is a long-term compatibility risk. JSON serialization goes through a custom mapper implementation rather than class-transformer or a standard library, adding a proprietary layer that teams have to learn and debug separately.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →