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

@chrono-os/health-nest

v0.1.1

Published

Health check para NestJS: GET /health com checks de dependência (banco, Redis, heartbeat) em paralelo, timeout por check, 200 ok ou 503 degraded, sem vazar erro interno no corpo; GET /health/live para liveness.

Readme

@chrono-os/health-nest

Health check para backend NestJS. GET /health roda os checks de dependência em paralelo, cada um com timeout próprio, e responde 200 {status:'ok'} ou 503 {status:'degraded'}. GET /health/live responde 200 enquanto o processo estiver vivo, sem tocar em nada.

Substitui o HealthController repetido no parque: uns devolvem 200 fixo sem olhar o banco (o orquestrador diz "saudável" com o Postgres fora), outros põem a mensagem do erro no corpo, e nenhum tem timeout (banco travado trava o health junto).

import { HealthModule, prismaPing } from '@chrono-os/health-nest'

@Module({
  imports: [
    HealthModule.forRootAsync({
      inject: [PrismaService],
      useFactory: (prisma: PrismaService) => ({
        checks: {
          db: prismaPing(prisma),                          // SELECT 1
          redis: async () => (await redis.ping()) === 'PONG',
          zapi: { run: () => !getZapiHealth().degraded, critical: false },
        },
        timeoutMs: 2000,
        info: { service: 'meu-backend' },
      }),
      decorators: [Public(), SkipThrottle()],              // libera do guard global
    }),
  ],
})
export class AppModule {}

Resposta:

{ "service": "meu-backend", "status": "degraded",
  "checks": { "db": { "status": "falha", "latencyMs": 2001 }, "redis": { "status": "ok", "latencyMs": 3 } } }

Regras

  • Um check falha quando lança, rejeita, devolve false ou passa do timeoutMs (default 3000, pode ser definido por check).
  • O corpo nunca leva o erro.ok/falha e a latência. O motivo vai para o log do servidor (Logger do Nest, ou onFailure(name, error)). Mensagem de erro do Prisma/pg costuma trazer host, usuário e nome do banco.
  • critical: false deixa o check só informativo: aparece no corpo, mas não derruba para 503.
  • Prisma não é dependência. prismaPing(client) chama $queryRawUnsafe('SELECT 1'); sqlPing(pool) serve pg. Qualquer () => Promise também vale.
  • path muda o prefixo (default 'health', aceita array); live: false tira a sub-rota de liveness.
  • Com setGlobalPrefix, exclua as rotas: app.setGlobalPrefix('api/v1', { exclude: ['health', 'health/live'] }).
  • Backend Fastify (sem Nest) usa só o núcleo: import { runHealthChecks } from '@chrono-os/health-nest/core'.

Peers: @nestjs/common e @nestjs/core 11.