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 🙏

© 2024 – Pkg Stats / Ryan Hefner

pino-prettier

v3.0.0

Published

a pretifier for pino logger json-output based on pino-pretty.

Downloads

3,790

Readme

pino-prettier

A terminal pino json-stream beautifier, based on pino-pretty

usage

Given that your svr.js uses pino and emits json-stream to stdout, then:

node svr.js | pino-prettier

installation

global

npm i -g 'pino-prettier'

After which, your machine has learnt a new command, pino-prettier to which you may pipe the stdoutput of your pino logger program.

local to project

npm i 'pino-prettier'

After which you may use it in your package.json scripts.

e.g.:

  "scripts": {
     ...
    "run": "node svr.js",
    "run:pretty": "node svr.js | pino-prettier",
    ...
  },

what's the difference from pino-pretty ?

  • meta objects are formatted using util.inspect which uses colors instead of the noisyjson.stringify
  • timestamp is "humanized" as just HH:MM:ss.l
  • the log channel is part of the formatted main line, and colorized with a unique color per channel.
  • level field appears first, to make its color distinctive against the indent black, and less confusing with the colorized channels.
  • fields are optimized for developer machine (filter out host, pid, version, etc)

Customization

This first version is customizable as far as CLI arguments supported by pino-pretty: it works by hacking the --config parameter, and injecting it's own config file, and does some hacky stuff on the way.

However, every customization that is supported by CLI arguments are stronger than the baked-in config file shipped with this package.

Have fun :)

history

  • 3.0.0 - modernized dependencies, improve tests, compatibility with modern versions of pino (transport target)
  • 2.0.3 - cli command changed from prettier to pino-prettier so it wont collide with the prettier lint tool.
  • 1.0.1 - first stable, however works only as CLI
  • 1.0.0 - was depricated for a bug, and unpublished after a cooldown period.