Docs / Start
FAQ — Migrating from NestJSSupported
What maps 1:1 from NestJS, what's deliberately different, and the feature-gap list.
Maps directly#
| NestJS | @zmdb/web |
|---|---|
@Controller/@Get… | same decorators |
| Providers / DI | Token + Container |
@Module | @Module + compileModule |
| Guards / Pipes / Interceptors / Filters | same four |
Lifecycle (onModuleInit…) | OnModuleInit/OnShutdown |
@nestjs/swagger | toOpenApi |
| Gateways (WS) | @Gateway/@Subscribe |
Test.createTestingModule | createTestApp |
Deliberately different#
- No
reflect-metadata— Stage-3 decorators native; the route table + DI graph resolve once at boot, zero runtime reflection. - No request-scoped providers by default — request data rides on
Ctx, not a rebuilt DI sub-tree. - No
ason the consumer surface — everything is inferred/typed. - Responses are transport-neutral descriptors (
{ status, headers, body }), so the Node and Fetch adapters share one handler. - Target ES2026+/ESNext — no downlevel of decorators in source.
Known feature gaps#
- File upload (multipart) · GraphQL · Microservices
Everything else (config, auth, authz, CORS, cookies/sessions, rate limiting, security headers, caching, logging) is a pattern on the existing primitives, documented in this Guides group rather than a bundled module — so there's no hidden magic and nothing to reflect.