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 🙏

© 2024 – Pkg Stats / Ryan Hefner

nestjs-swagger-hide-on-prod

v1.0.8

Published

<p align="center"> <a href="http://nestjs.com/" target="blank"><img src="https://nestjs.com/img/logo-small.svg" width="120" alt="Nest Logo" /></a> </p> <p align="center">A progressive <a href="http://nodejs.org" target="blank">Node.js</a> framework for

Downloads

133

Readme

Nestjs Swagger Hide on Prod

Description

Exclude your nestjs controller or endpoint from swagger documentization on production env.

Installation

$ yarn add nestjs-swagger-hide-on-prod

or

$ npm i --save nestjs-swagger-hide-on-prod

Getting Started

In default, when NODE_ENV is set to PROD or PRODUCTION, following decorators will exclude the whole controller or specific endpoint

  • @SwaggerHideControllerOnProd
  • @SwaggerHideEndpointOnProd

To exclude whole controller on prod :

@Controller('foo')
@ApiTags('Foo API')
@SwaggerHideControllerOnProd() // Add this line to exclude FooController from swagger when process is on production environment
export class FooController {
  constructor(private readonly fooService: FooService) {}
  @Get(':fooId')
  searchFoos(): Promise<any[]> {
    return Promise.resolve([]);
  }

  @Post()
  createFoo(): Promise<any> {
    return Promise.resolve();
  }
}

To Exclude specific endpoint only on prod :

@Controller('foo')
@ApiTags('Foo API')
export class FooController {
  constructor(private readonly fooService: FooService) {}
  @Get(':fooId')
  searchFoos(): Promise<any[]> {
    return Promise.resolve([]);
  }

  @Post()
  @SwaggerHideEndpointOnProd() // Exclude POST /foo endpoint from swagger on prod env
  createFoo(): Promise<any> {
    return Promise.resolve();
  }
}

To customize exclusion condition you can use

  • @SwaggerHideController
  • @SwaggerHideEndpoint

instead. Input parameter could be static boolean or a function, which returns a boolean value.

@Controller('foo')
@ApiTags('Foo API')
export class FooController {
  constructor(private readonly fooService: FooService) {}

  @Get(':fooId')
  @ApiOperation({
    summary: 'Search foos info',
    description: 'This method is depreacted. Please, use GET "v2" instaed',
  })
  @SwaggerHideEndpoint(() => {
    return moment(new Date()).isAfter(`2022-12-31`);
    // After year 2022, this method would be excluded from swagger documentization
  })
  veryOldFooSearchApi(): Promise<any[]> {
    return Promise.resolve([]);
  }

  @Get('v2/:fooId')
  @ApiOperation({
    summary: `Search foos info`,
    description: `Get information matches id`,
  })
  brandNewFooSearchApi(): Promise<any[]> {
    return Promise.resolve([]);
  }
}