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

@quo-digital/nominex-authorization-tokens-client

v1.3.4

Published

TCP Tokens Client for Nominex

Readme

@quo-digital/nominex-authorization-tokens-client

Descripción

Cliente TCP para validar tokens de autorización en Nominex. Este paquete proporciona un módulo NestJS que se conecta a un microservicio de tokens mediante TCP para validar tokens de autorización.

📦 Instalación

Para instalar el paquete, usa npm:

npm install @quo-digital/nominex-authorization-tokens-client

🚀 Uso

Configuración básica

Primero, asegúrate de configurar las variables de entorno necesarias:

MS_TOKENS_HOST=localhost
MS_TOKENS_PORT=3001

Importar el módulo en tu aplicación NestJS

import { Module } from '@nestjs/common';
import { TcpClientModule } from '@quo-digital/nominex-authorization-tokens-client';

@Module({
  imports: [TcpClientModule],
  // ... otros módulos
})
export class AppModule {}

Usar el servicio de tokens

import { Injectable } from '@nestjs/common';
import { TokensService, ValidarTokenRequestDto } from '@quo-digital/nominex-authorization-tokens-client';

@Injectable()
export class MiServicio {
  constructor(private readonly tokensService: TokensService) {}

  async validarToken(token: string, solicitanteId: string) {
    const request: ValidarTokenRequestDto = {
      token,
      solicitanteId,
      payload: {
        // datos adicionales si es necesario
      },
    };

    const resultado = await this.tokensService.validarToken(request);
    
    if (resultado.valido) {
      console.log('Token válido');
    } else {
      console.error('Token inválido:', resultado.error);
    }
    
    return resultado;
  }
}

📋 Exports

El paquete exporta los siguientes elementos:

  • TcpClientModule: Módulo NestJS que configura el cliente TCP
  • TokensService: Servicio para validar tokens
  • ValidarTokenRequestDto: DTO para la solicitud de validación
  • ValidarTokenResponseDto: DTO para la respuesta de validación
  • VALIDAR_TOKEN_PATTERN: Patrón de mensaje TCP usado para la comunicación

🔧 Variables de entorno requeridas

  • MS_TOKENS_HOST: Host del microservicio de tokens (ej: localhost o tokens-service)
  • MS_TOKENS_PORT: Puerto del microservicio de tokens (ej: 3001)

⚠️ Manejo de errores

El servicio maneja automáticamente los errores de conexión TCP y retorna un objeto con valido: false y un mensaje de error descriptivo cuando no puede conectarse al microservicio.

📝 Dependencias

  • @nestjs/common: ^11.0.9
  • @nestjs/microservices: ^11.1.13
  • class-validator: ^0.14.1
  • rxjs: ^7.8.1

📄 Licencia

MIT

👤 Autor

Huetzin Sotelo