Limitations & roadmap

Limitations & roadmap

This page is intentionally honest: what does not work well yet and what we are aiming for next. It is not a dated release plan—order and timing can change. For shipped changes, see the Changelog.

Current limitations

Area	What to expect
WebSockets on Node.js	The WebSocket plugin responds with HTTP 501 on Node.js. Upgrades work on Bun and Deno. For real-time on Node today, use another stack or run the API on Bun/Deno for the WS surface.
GraphQL	The GraphQL plugin and decorators are still maturing. Treat them as experimental for production until you have validated your scenario.
ORM integrations	Drizzle has first-class DI helpers (registerDrizzle, @InjectDB). Prisma and TypeORM are not yet at the same level of built-in, documented integration—you can still use them directly inside your services.
Pre-1.0	Public APIs may evolve between minors. Always check the changelog before upgrading.

Planned updates (directional)

Priorities the maintainers care about; not a promise of order or date.

1. ORM choice — Make Drizzle, Prisma, and TypeORM practical, documented options so teams can pick an ORM without fighting the framework.
2. WebSockets on Node.js — Replace the Node 501 path with a real upgrade integration (e.g. ws or equivalent) so the same decorator-based API works on Node as on Bun/Deno.
3. CLI scaffolding — Optional code generation (e.g. controller + route + test skeleton), in the spirit of tools like Feathers’ generate service, kept small and maintainable.
4. GraphQL — Hardening and docs after REST, caching, WebSockets-on-Node, and ORM stories are in better shape (lower priority than the items above).

How to contribute or discuss

• Shipped work: Changelog and the GitHub repository.
• Ideas and proposals: GitHub Discussions.