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

@payk/nestjs-response-utils

v2.2.2

Published

NestJS Response Transformers, Interceptors and utils

Downloads

23

Readme

Build Status

Installation

npm install @payk/nestjs-response-utils

What does it do?

Quick Start

Add a decorator on top of your method or controller

@UseInterceptors(new LoggingInterceptor(), new TransformResponseInterceptor(ResponseKYCDto))

The LogginInterceptor can also be added globally according to NestJS documentation.

The TransformResponseInterceptor accepts in his ctor the object it's supposed to transform and also a mapping function if the properties are named differently.

Why & How

Our operation mode is that Dto goes into the controller and then into the service. And the service works with Models (DB Models mainly). The service then returns to the controller the Model and the controller transforms it into a Response DTO. To remove the boilerplate, the service should use a MetaResponse object and the controller the TransformResponseInterceptor that will do the transformation of the MetaResponse into the ResponseDTO.

The Service gets a RequestDTO and returns a MetaRespone<Model> created by the MetaResponseGenerator to the controller.

MetaResponse

Do create a MetaResponse we have a MetaResponseGenerator class.

// Return an object (Model) and the require ResponseCode (HttpResponse normally)
MetaResponseGenerator.generateByResponseCode(
    dbModel,
    ResponseCodes.OK,
  );

// Return an Error, no object needed.
MetaResponseGenerator.generateAnErrorResponse(
    ResponseCodes.NOT_FOUND,
  );

// Return an HttpStatus error
MetaResponseGenerator.generateErrorByStatus(
  HttpStatus.OK,
  { error: 'object' }
)

ResponseCode

The ResponseCode object assists in returning errors mainly. A few come by default in the ResponseCodes class. More can be initiated using the ResponseCode ctor

LoggingInterceptor

The logging interceptor will log the request and response to the service.

Masking Data

In order to mask data that shouldn't be logged, the LoggingInterceptor supports getting an array in his constructor of property names that should be masked.

new LoggingInterceptors(['propertyName','properyThatShouldBeMasked'])

Assuming the following Json:

{
  name: 'Dan',
  test: 'ing',
  propertyName: 'I'll be masked',
  inner: {
    here: 'there',
    properyThatShouldBeMasked: 123,
    propertyName: 1111999
  }
}

Will result in the following:

{
  name: 'Dan',
  test: 'ing',
  propertyName: '--REDACTED--',
  inner: {
    here: 'there',
    properyThatShouldBeMasked: '--REDACTED--',
    propertyName: '--REDACTED--'
}