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

@crypolt/crplogger

v1.0.3

Published

Lightweight async JSON logger with automatic request_id, structured logs, global initialization and zero dependencies.

Readme

@crypolt/crplogger

Lightweight, zero-dependency, high-performance asynchronous structured JSON logger for Node.js with automatic request_id propagation via AsyncLocalStorage.

Features

  • Zero dependencies
  • Asynchronous non-blocking queue
  • Automatic request_id propagation
  • Fully structured JSON logs
  • Global logger instance (initLogger, getLogger)
  • Works with Elastic, Loki, Kibana, Grafana
  • Error stack trace serialization
  • Minimal overhead and extremely fast

Installation

npm install @crypolt/crplogger

Quick Start

import { initLogger } from '@crypolt/crplogger'

const logger = initLogger({ level: 'INFO' })

logger.info('Server started', {
  Payload: { port: 8080 }
})

Example output:

2025-01-15T10:25:10.123Z {"Level":"INFO","Host":"app01","Message":"Server started","Payload":{"port":8080,"RequestID":"8e91a380-..."}}

Request ID Context

import { runWithRequestId, getRequestId, getLogger } from '@crypolt/crplogger'

runWithRequestId(() => {
  const logger = getLogger()
  logger.info('Inside context', {
    Payload: { id: getRequestId() }
  })
})

Global Logger

import { initLogger, getLogger } from '@crypolt/crplogger'

initLogger({ level: 'DEBUG' })

const logger = getLogger()

logger.debug('Debug message')
logger.error(new Error('Failure'))

API

initLogger(config)

Initialize global logger (singleton).

getLogger()

Returns the global logger instance.

createLogger(config)

Creates a standalone logger instance.

Logger Methods

  • logger.trace(message, meta?)
  • logger.debug(message, meta?)
  • logger.info(message, meta?)
  • logger.warn(message, meta?)
  • logger.error(message or Error, meta?)
  • logger.fatal(message or Error, meta?)

LogMeta structure

{
  Payload?: Record<string, any>,
  request_id?: string,
  stack?: string,
  errorMsg?: string,
  Source?: any
}

Integration Examples

Express

import express from 'express'
import { initLogger, runWithRequestId, getLogger } from '@crypolt/crplogger'

initLogger({ level: 'INFO' })

const app = express()

app.use((req, res, next) => {
  runWithRequestId(() => {
    const logger = getLogger()
    logger.info('Incoming request', {
      Payload: {
        method: req.method,
        url: req.url
      }
    })
    next()
  })
})

app.get('/', (req, res) => {
  const logger = getLogger()
  logger.info('Handled root route')
  res.send('OK')
})

app.listen(3000)

Fastify

import Fastify from 'fastify'
import { initLogger, runWithRequestId, getLogger } from '@crypolt/crplogger'

initLogger({ level: 'INFO' })

const app = Fastify()

app.addHook('onRequest', (req, res, next) => {
  runWithRequestId(() => {
    const logger = getLogger()
    logger.info('Incoming request', {
      Payload: { url: req.url }
    })
    next()
  })
})

app.get('/', async () => {
  const logger = getLogger()
  logger.info('Fastify root hit')
  return { ok: true }
})

app.listen({ port: 3000 })

Kafka Consumer

import { Kafka } from 'kafkajs'
import { initLogger, runWithRequestId, getLogger } from '@crypolt/crplogger'

initLogger({ level: 'INFO' })

const kafka = new Kafka({ clientId: 'svc', brokers: ['localhost:9092'] })
const consumer = kafka.consumer({ groupId: 'group1' })

await consumer.connect()
await consumer.subscribe({ topic: 'events' })

await consumer.run({
  eachMessage: async ({ message }) => {
    runWithRequestId(() => {
      const logger = getLogger()
      logger.info('Processing message', {
        Payload: { value: message.value.toString() }
      })
    })
  }
})

Example Log Output

2025-01-15T10:30:12.114Z {"Level":"INFO","Host":"srv01","Message":"Incoming request","Payload":{"method":"GET","url":"/","RequestID":"d59f5e1b-..."}}
2025-01-15T10:30:12.115Z {"Level":"INFO","Host":"srv01","Message":"Handled root route","Payload":{"RequestID":"d59f5e1b-..."}}

License

Information / Contact

-- telegram @crypolt

MIT License