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

@nebulae/tpiv2-interop-rest

v0.0.1

Published

Cliente REST resiliente con validación JSON Schema y manejo de errores

Readme

@nebulae/tpiv2-interop-rest

Cliente REST resiliente con validación JSON Schema y manejo de errores.

Instalación

npm install @nebulae/tpiv2-interop-rest @nebulae/tpiv2-interop-auth

Uso

Cliente REST Básico

import { RestClient } from '@nebulae/tpiv2-interop-rest';

const client = new RestClient({
  baseUrl: 'https://api.example.com',
  retry: {
    maxRetries: 3,
    initialDelay: 1000,
  },
});

const response = await client.get('/usuarios/123');
console.log(response.data);

Con Autenticación

import { RestClient } from '@nebulae/tpiv2-interop-rest';
import { AuthClient } from '@nebulae/tpiv2-interop-auth';

const authClient = new AuthClient({ /* config */ });

const restClient = new RestClient({
  baseUrl: 'https://api.example.com',
  authClient, // Agrega automáticamente el token
});

const response = await restClient.get('/protected-resource');

Con Validación de Esquemas

interface Usuario {
  id: number;
  nombre: string;
  email: string;
}

const response = await restClient.get<Usuario>('/usuarios/123', {
  responseSchema: {
    type: 'object',
    properties: {
      id: { type: 'number' },
      nombre: { type: 'string' },
      email: { type: 'string', format: 'email' },
    },
    required: ['id', 'nombre', 'email'],
  },
});

Con Circuit Breaker

Cada RestClient incluye un CircuitBreaker propio. Si el servicio remoto falla seguidas veces, el circuit breaker se abre (OPEN) y rechaza las llamadas subsiguientes sin realizar el request HTTP, evitando saturar un endpoint ya degradado.

import { RestClient } from '@nebulae/tpiv2-interop-rest';
import { CircuitOpenError } from '@nebulae/tpiv2-interop-core';

const client = new RestClient({
  baseUrl: 'https://api.example.com',
  circuitBreaker: {
    enabled: true,
    failureThreshold: 5,      // abre tras 5 fallas consecutivas
    halfOpenTimeoutMs: 30000, // intenta recuperar tras 30 s
    successThreshold: 2,      // cierra tras 2 éxitos en HALF_OPEN
  },
});

// Escuchar eventos de transición de estado
client.circuitBreaker.on('circuit:open', (event) => {
  console.warn(`[CB] Circuito ABIERTO — fuente: ${event.source}, fallas: ${event.consecutiveFailures}`);
});
client.circuitBreaker.on('circuit:half-open', () => {
  console.info('[CB] Circuito en HALF_OPEN — sondeando recuperación');
});
client.circuitBreaker.on('circuit:close', () => {
  console.info('[CB] Circuito CERRADO — servicio recuperado');
});

// Manejar el rechazo cuando el circuito está abierto
try {
  const response = await client.get('/resource');
} catch (error) {
  if (error instanceof CircuitOpenError) {
    console.error(`Circuito abierto (estado: ${error.circuitState}), request rechazado sin llamada HTTP`);
  }
}

Estados del circuit breaker:

| Estado | Descripción | |--------|-------------| | CLOSED | Operación normal; fallas se acumulan | | OPEN | Todas las requests son rechazadas con CircuitOpenError | | HALF_OPEN | Se permite una sonda; un éxito cierra, un fallo reabre |

Comportamiento especial para errores de autenticación: un único AuthenticationError (token inválido/expirado) abre el circuito de inmediato (source: 'auth'), sin esperar el umbral failureThreshold.

API

Ver documentación completa.