Skip to main content
These crates close NestJS gaps that nestrs cannot rebuild on Axum. They are workspace members, not feature flags on nestrs. Add only the crates you use. They depend on nestrs-core (or nothing) so they do not cycle with the façade crate. Fastify remains out of scope (ADR-0001). nestrs-drizzle stays carved out of workspace members.
Pages on docs.rs appear after the crate is published to crates.io. Until then, this section is the canonical guide.

Crates in this section

nestrs-socketio

Socket.IO via socketioxide — Nest @nestjs/platform-socket.io.

nestrs-lambda

AWS Lambda / API Gateway — listen_lambda(router).

nestrs-auth-strategy

JwtStrategy and LocalBasicStrategy on AuthStrategy.

nestrs-better-auth

Nest the better-auth.rs router and guard session cookies.

nestrs-bullmq

BullMQ Redis key-layout producer for Node workers.

nestrs-saml

SAML 2.0 SP-initiated redirect + SamlResponseValidator.

nestrs-ldap

LDAP simple bind — passport-ldap analogue.

nestrs-sea-orm

SeaORM for_root_async — TypeORM / Sequelize analogue.

NestJS mapping

How they attach

Most adapters return an Axum Router, a Tower layer, or a DynamicModule. Merge them with NestFactory::create_with_modules or into_router() — they are not nestrs = { features = [...] } flags.