npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

incident-management-commons

v1.0.13

Published

Common shared library between microservices with common definitions like errors types, filters, transformers, base entities, services and utilities.

Downloads

73

Readme

Common Library

Common shared library between microservices with common definitions like errors types, filters, transformers, base entities, services and utilities.

Bootstrapping

  • configureMicroservice: Function that configures a nest application with the transformers, filters and logger services.

Common

  • BaseEntity: It is an abstract class that works as base type for all the entities, this base entity depend of typeorm.

  • BusinessError: It is a base class for all custom errors, it is required that custom errors inherit from this class so that they could be interpreted and formatted by our error filters.

Filter

  • CustomExceptionFilter: This is a nestjs filter that handle custom error responses.

Interceptor

  • TransformInterceptor: This is a nestjs interceptor that apples a common controller response for all requests.

Modules

  • SharedModule: This is a shared module that exports some shared services within the application like the logger service, it is recommended to import this function in the main module (ex. AppModule).
  • JwtAuthModule: Reusable module that adds JWT validation using Passport strategy jwt. Useful to protect microservices with shared auth logic. Exports strategy, PassportModule, and JwtModule.
    See JWT Auth Module section for detailed configuration and usage.

Requirements

  • NodeJs v16 or greater
  • NestJs framework v.9 or equivalent

Usage

  1. Install the library in you project

    npm install incident-managment-commons
  2. Import IncidentManagementSharedModule in the main module of your application.

    import { Module } from '@nestjs/common';
    
    import { IncidentManagementSharedModule } from 'incident-managment-commons';
    
    import { AppController } from './app.controller';
    
    @Module({
      imports: [
        IncidentManagementSharedModule,
      ],
      controllers: [AppController],
    })
    export class AppModule {}
    
  3. Import and run the configureMicroservice function within your bootstrap application function

    import { ConfigService } from '@nestjs/config';
    import { NestFactory } from '@nestjs/core';
    
    import { configureMicroservice } from 'incident-managment-commons';
    
    import { AppModule } from './app.module';
    
    async function bootstrap() {
      const app = await NestFactory.create(AppModule);
    
      configureMicroservice(app, {
        title: 'Example Service',
        description: 'API for example service',
        version: '1.0',
        basePath: 'example',
      });
    
      const configService = app.select(AppModule).get(ConfigService);
    
      const port = configService.get('PORT') || 3001;
    
      await app.listen(port);
    }
    bootstrap();

JWT Auth Module

  1. Add the following environment variables to your .env file:

      JWT_SECRET=your-jwt-secret
  2. Import JwtAuthModule in the main module of your application:

    import { Module } from '@nestjs/common';
    import { JwtAuthModule } from 'incident-managment-commons';
    
    @Module({
      imports: [
        JwtAuthModule,
      ],
    })
    export class AppModule {}
  3. The JwtAuthGuard is typically applied globally using app.useGlobalGuards(...) during application bootstrap, so you don't need to use @UseGuards(JwtAuthGuard) manually on each controller.

  4. If you want to make a route public (no authentication required), use the @Public() decorator:

    import { Controller, Get } from '@nestjs/common';
    import { Public } from 'incident-managment-commons';
    
    @Controller('healthz')
    export class HealthController {
      @Get()
      @Public()
      getHealthStatus() {
        return { status: 'ok' };
      }
    }