A collection of Badass modules and utilities to help you level up your NestJS application.
| Package | Description | Version | Changelog |
|---|---|---|---|
@golevelup/nestjs-common |
Common types, mixins |  |
changelog |
@golevelup/nestjs-discovery |
DiscoveryModule for finding providers, controllers and method handlers from your NestJS app that have certain metadata |
 |
changelog |
@golevelup/nestjs-rabbitmq |
A NestJS native module for RabbitMQ that supports both RPC and Publish/Subscribe messaging patterns |  |
changelog |
@golevelup/nestjs-modules |
A Dynamic Module helper. Useful for configuring once and importing anywhere else |  |
changelog |
@golevelup/nestjs-hasura |
Super charged Hasura Event Handlers and other utilities for seamlessly integrating Hasura with NestJS |  |
changelog |
@golevelup/nestjs-graphql-request |
Dependency Injection for GraphQLClient. Make type safe requests to third party GQL APIs |  |
changelog |
@golevelup/nestjs-webhooks |
Middlewares and helpers for processing webhooks |  |
changelog |
@golevelup/nestjs-stripe |
Stripe client and webhook processing |  |
changelog |
@golevelup/ts-jest |
Jest utilities for making testing NestJS applications easier. |  |
changelog |
Contributions welcome! Read the contribution guidelines first.
To ensure only relevant packages are published, version bumps must be done manually. This approach avoids relying on Git tags, which tend to result in higher conflict rates. Once the version is updated in a package’s package.json, it can be published individually.
Historically, any change to a shared library would trigger a publish for all packages — even those that hadn’t changed. This manual bumping strategy prevents unnecessary publishes and keeps versioning meaningful.
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!