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

pino-charm

v0.7.0

Published

Minimal pino formatter

Readme

pino-charm

Minimal pino formatter.

Screenshot

About

pino-charm is a small pino transport for readable terminal logs. It keeps the output compact, adds colored levels and makes errors easier to scan.

Installation

# pnpm
pnpm add pino-charm -D

# yarn
yarn add pino-charm -D

# npm
npm install pino-charm -D

Usage

import pino from 'pino'

const logger = pino({
  transport: {
    target: 'pino-charm'
  }
})

logger.debug('Starting server...')
logger.info({ port: 3000 }, 'Server started')
logger.warn({ duration: 1200, path: '/users' }, 'Slow request')
logger.error(new Error('Database connection failed'))

Best practices

A few small things that make logs nicer to read:

Error causes

Use pino's errWithCause serializer to show the cause field for errors.

import pino from 'pino'

const logger = pino({
  serializers: {
    err: pino.stdSerializers.errWithCause
  },
  transport: {
    target: 'pino-charm'
  }
})

Nested context

Use nestedKey to keep application fields separate from pino's own fields. This helps avoid collisions with keys like time, level, msg or err, while keeping the formatted output clean.

import pino from 'pino'

const logger = pino({
  nestedKey: 'context',
  transport: {
    target: 'pino-charm',
    options: {
      nestedKey: 'context'
    }
  }
})

logger.info({ port: 3000, time: true }, 'Server started')

Inspiration

Inspired by these lovely packages:

License

MIT