Open-source NestJS integrations

Native-feeling libraries for serious NestJS applications.

Nest Native packages bring decorator-first APIs, dependency injection, testing utilities, and production-minded docs to tools that TypeScript backend teams already love.

Explore projects View organization

Decorators @Inject*

Modules forRoot()

Features forFeature()

Transactions @Transactional()

Projects

Packages

Published

@nest-native/drizzle

Nest-native Drizzle ORM integration with modules, DI, repositories, named connections, transaction decorators, and runnable samples.

Docs GitHub npm

Published

@nest-native/trpc

Decorator-first tRPC for NestJS, designed around routers, procedures, dependency injection, enhancers, and type-safe client consumption.

Docs GitHub npm

Published

@nest-native/ai-sdk

Decorator-first NestJS streaming primitive for the Vercel AI SDK that preserves the full Nest enhancer pipeline — guards, interceptors, pipes, and filters around streamed responses.

Docs GitHub npm

Published

@nest-native/asyncapi

Decorator-first AsyncAPI 3.0 documentation generator for NestJS event-driven services — the AsyncAPI counterpart to @nestjs/swagger.

Docs GitHub npm

Published

@nest-native/kafka

Decorator-first NestJS Kafka integration built on Confluent's officially supported @confluentinc/kafka-javascript client, with full enhancer-pipeline support.

Docs GitHub npm

Published

@nest-native/messaging

Transactional outbox and idempotent inbox for NestJS — atomic "write rows and publish an event" on Drizzle (SQLite/Postgres), delivered over Kafka with effective exactly-once consumption.

Docs GitHub npm

Reference

reference-app

Production reference app for the Nest Native stack — feature modules, multi-tenant context, cross-service transactions, transactional outbox, and real-database tests.

GitHub

Philosophy

Feel native. Stay honest.

A Nest Native package should feel like it belongs next to official NestJS integrations: modules, decorators, dependency injection, lifecycle hooks, testing tools, and clear documentation.

It should also respect the tool it integrates. Drizzle should still feel SQL-first. tRPC should still preserve end-to-end type safety. Future integrations should only exist when they solve a real gap without hiding the underlying tool.

No unnecessary runtime dependencies.
No hidden magic where explicit application code is clearer.
No public helper APIs before samples prove they are useful.
Production confidence through CI, coverage, samples, and docs.