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-filter

v2.0.0

Published

A transport for Pino to filter logs based on logger names

Downloads

10,650

Readme

pino-filter

npm version Build Status Coverage Status js-standard-style

Lead maintainer: James Sumners

pino-filter is a transport for Pino that allows filtering of log lines based on logger names, similar to the funtionality of filters in the debug module.

Logs that match any filters are written to stdout. By default, pino-filter will pass through all received logs at the info level or higher. To define filters, a configuration file must be supplied that provides a mapping of filters to log levels. For example, you can supply a simple JSON file:

{
  "levels": {
    "*": "info",
    "foo:bar": "debug",
    "baz:*": "trace"
  }
}

Usage

$ node the-app.js | pino-filter ./config.json

Config

module.exports = {
  levels: {
    '*': 'info', // catch-all filter
    'foo:bar': 'debug',
    'baz:*': 'trace'
  },
  values: {
    fatal: 60,
    error: 50,
    warn: 40,
    info: 30,
    debug: 20,
    trace: 10
  }
}
  • levels: a mapping of filters (keys) to log levels (level names). Note: the wildcard * may only be used at the end of a filter, e.g. foo:* is valid but foo:*:bar is not.
  • values: a mapping of level names to their numeric value. The default is set to the standard Pino levels. If custom levels are defined in the application, those level values should be defined here.

Note: the configuration file can be reloaded at runtime by sending the SIGHUP signal to the pino-filter process.