NestJS integration module #268

Activity

1. adenhertog

   added this to the Phase 4: Ecosystem & platform milestone on Sep 30, 2026
2. adenhertog

   added

   enhancementNew feature or requestNew feature or request

   roadmapPart of the project roadmapPart of the project roadmap

   on Sep 30, 2026
3. adenhertog

   marked this as blocked on Sep 30, 2026

   • Handler and workflow test helpers #265
4. adenhertog

   marked this as blocking 4 issues on Oct 1, 2026

   • Project scaffolding: npm create bus-app templates #269
   • Quick-start tutorial and runnable examples/ with docker compose #252
   • Document features that exist but aren't in the docs #253
   • Docs: concepts page and comparison with Temporal, BullMQ and NestJS #254
5. adenhertog commented on Oct 7, 2026

   

   adenhertog

   on Oct 7, 2026

   ContributorAuthor

   More actions

   Accepted design (maintainer, 2026-10-07)

   • Package: @node-ts/bus-nestjs in packages/bus-nestjs. Peers @nestjs/common and @nestjs/core ^11.0.0 || ^12.0.0 (only APIs both have), @node-ts/bus-core ^2.0.0. CI tests Nest 12.
   • Configuration: BusModule.forRoot({ configure }) and forRootAsync({ imports, inject, useFactory }) take a factory that returns an unbuilt BusConfiguration, so every builder method works and nothing is duplicated. The module adds the Nest container adapter, the discovered handlers and workflows, withInterruptSignals([]) and Nest's Logger (unless withLogger() is used), then builds.
   • Registration: BusModule.forFeature({ handlers, workflows }) and forFeatureAsync({ inject, useFactory }) register class and function handlers and workflows (function handlers get dependencies through inject). @BusHandler() and @BusWorkflow(), made with DiscoveryService.createDecorator(), are optional sugar for classes. No decorators on messages.
   • Injection and several buses: the default bus is injected as BusInstance. Named buses use forRoot({ name }), getBusToken(name) and @InjectBus(name), with forFeature({ bus }) and @BusHandler({ bus }). Each bus has its own container adapter.
   • Lifecycle: built in the provider factory; initialize() and start() in onApplicationBootstrap (start() skipped for buses that don't poll, through a small public getter in bus-core); stop() in onModuleDestroy; dispose() in onApplicationShutdown. lifecycle: 'manual' leaves starting to the app. Graceful SIGTERM needs app.enableShutdownHooks().
   • Provisioning: bus provision also accepts a module that exports a built, uninitialized BusInstance (or a function returning one), and bus.mjs exits explicitly. createBusForProvisioning(AppModule, { bus? }) boots the app with the bus' lifecycle off and returns the bus.
   • Scopes: singleton providers are resolved with moduleRef.get. Request-scoped and transient ones are resolved with one ContextId per received message, with { message, attributes } registered as REQUEST. Bootstrap fails with a named error if a class handler or workflow isn't a provider.
   • Tests: Nest 12 is ESM-only, so Jest runs with NODE_OPTIONS=--experimental-vm-modules (falling back to transformIgnorePatterns if an existing suite breaks). Tests use Test.createTestingModule with InMemoryQueue and the existing handlerContext() fakes.
6. adenhertog

   marked this as blocking 2 issues on Oct 8, 2026

   • Pass a per-delivery key to ContainerAdapter.get, so request scopes aren't shared across retries #353
   • Read configureWorkflow() without resolving the class workflow at registration #354
7. adenhertog

   closed this as completedin #352on Oct 8, 2026