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

@fabbahiense/pulsar-next

v0.2.0

Published

Next.js SDK for Pulsar observability platform — App Router instrumentation, route handler wrapper, edge-safe middleware, client error capture

Downloads

135

Readme

@fabbahiense/pulsar-next

Next.js SDK para o Pulsar. Funciona com App Router (Next 13+).

Instalacao

npm install @fabbahiense/pulsar-next

Setup

1. instrumentation.ts (raiz do projeto)

export async function register() {
  if (process.env.NEXT_RUNTIME === 'nodejs') {
    const { initPulsar } = await import('@fabbahiense/pulsar-next')
    initPulsar({
      url: process.env.PULSAR_URL!,
      apiKey: process.env.PULSAR_API_KEY!,
      serviceName: 'web',
    })
  }
}

Isso intercepta console.log/info/warn/error automaticamente. Cada log vai pro Pulsar com traceId se estiver dentro de um request handler envolvido pelo withPulsar.

2. Route handlers (opcional, mas recomendado)

import { withPulsar } from '@fabbahiense/pulsar-next'

export const GET = withPulsar(async (req: Request) => {
  console.log('Fetching user')
  return Response.json({ ok: true })
})

Cada request ganha traceId (do header x-trace-id ou auto-gerado). Logs dentro do handler herdam o mesmo traceId. Por padrão emite 1 log automático no fim da request com método/URL/status/duração.

2b. Capturar request/response bodies e headers

export const POST = withPulsar(async (req: Request) => {
  const data = await req.json()
  const result = await processCheckout(data)
  return Response.json(result)
}, {
  captureBody: true,
  captureResponseBody: true,
  maxBodySize: 10240,            // 10KB por body, truncado se maior
  redactKeys: ['cpf', 'cardNumber'],
})

Cada chave redacta recursivamente em bodies e headers. Default redact: password, token, secret, authorization, cookie, api-key.

No painel lateral do Pulsar aparecem as seções Request body, Response body, Request/Response headers, Query e Path params com syntax highlight + copy.

3. Logger estruturado

import { createLogger } from '@fabbahiense/pulsar-next'

const log = createLogger({ serviceName: 'auth' })

log.info('User logged in', { userId: '123' })
log.error('Login failed', { reason: 'invalid_password', userId: '123' })

4. Capturar erros do client (error.tsx)

'use client'
import { initPulsarClient, captureException } from '@fabbahiense/pulsar-next/client'
import { useEffect } from 'react'

initPulsarClient({
  url: process.env.NEXT_PUBLIC_PULSAR_URL!,
  apiKey: process.env.NEXT_PUBLIC_PULSAR_CLIENT_KEY!,
})

export default function Error({ error }: { error: Error }) {
  useEffect(() => {
    captureException(error)
  }, [error])
  return <div>Algo deu errado</div>
}

Variaveis de ambiente

PULSAR_URL=https://seu-pulsar.com
PULSAR_API_KEY=psk_xxx

Pro client component, use prefixo NEXT_PUBLIC_.

Notas

  • Edge runtime (middleware.ts) nao tem AsyncLocalStoragewithPulsar so funciona em route handlers Node.
  • Serverless (Vercel): chame await flushPulsar() antes do response retornar pra garantir que logs nao se percam.
  • Captura de erros server-side: withPulsar ja captura erros que escapam do handler. Pra capturar manualmente, use captureException(err).

License

MIT