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

@chiper-inc/i18n-chiper

v1.0.0

Published

i18n chiper for nestjs

Downloads

14

Readme

Nestjs i18n Chiper

Table of Contents

Description

This nestjs module offers a simple way to use some functionalities from the i18n-chiper.

Motivation

As team we need to translate our application in different languages, that code is always the same, so that's we wrote this module to make it easier to translate our application.

Requirements

  1. Nodejs LTS.
  2. Have nestjs project.

Usage

Install

npm i nestjs-i18n-chiper -S -E

OR

yarn add nestjs-i18n-chiper

Module Initialization

Import and add I18nChiperModule it to the imports array of module for which you would like to discover handlers. It may make sense for your application to do this in a shared module or to re-export it so it can be used across modules more easily. You can check this docs in order to get more information about modules.

For example, we're using I18nChiperModule in src/app.module.ts:

@Module({
  imports: [
    // i18n chiper module
    I18nChiperModule.registerAsync({
      imports: [ConfigModule],
      inject: [ConfigService],
      useFactory: (configService: ConfigService) => {
        return {
          i18nLocalesBaseUrl: configService.get<string>(
            'config.i18n.localesUrl',
          ),
        };
      },
    }),
  ],
  controllers: [AppController],
  providers: [
    AppService,
    {
      provide: APP_FILTER,
      useClass: HttpExceptionFilter,
    },
  ],
})
export class AppModule {}

Filter

The other important aspect it's the custom implementation of a filter, in favor of the translation of the error messages.

You can check this docs in order to get more information about guards.

For example we wrote a custom filter called HttpExceptionFilter:

import {
  ArgumentsHost,
  Catch,
  ExceptionFilter,
  HttpException,
} from '@nestjs/common';

import { I18nChiperService } from 'nestjs-i18n-chiper';

@Catch(HttpException)
export class HttpExceptionFilter<T extends HttpException>
  implements ExceptionFilter
{
  constructor(private readonly i18nService: I18nChiperService) {}

  catch(exception: HttpException, host: ArgumentsHost) {
    const ctx = host.switchToHttp();

    const response = ctx.getResponse();
    const request = ctx.getRequest();

    const statusCode = exception.getStatus();
    const exceptionResponse = exception.getResponse();

    const httpException =
      typeof exceptionResponse === 'string'
        ? {
            message: exceptionResponse,
          }
        : (exceptionResponse as any);

    if (httpException.key) {
      httpException.message = this.i18nService.translate({
        defaultTranslation: httpException.defaultMessage,
        key: httpException.key,
        options: httpException.args,
      });
    }

    response.status(statusCode);
    response.send({
      error: exception.name,
      statusCode: statusCode,
      defaultMessage: httpException.defaultMessage,
      message: httpException.message,
      timestamp: new Date().toISOString(),
      path: request.url,
      key: httpException.key || 'common.error',
      args: httpException.args || {},
    });
  }
}