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

@bonniernews/exp-logger

v4.1.0

Published

Simple bootstrapping of pino logger

Downloads

4,850

Readme

exp-logger

Simple logger package to unify how logging is done with (configurable) remapping

NPM


defaults

  • trace -> DEBUG
  • debug -> DEBUG
  • info -> INFO
  • warn -> WARNING
  • error -> ERROR
  • fatal -> CRITICAL

options

  logLevel // defaults to info
  mixin  // pino mixins, passed down to pino as is
  formatLog  // pino formatter.log function, passed down to pino as is

example


const logger = require('@bonniernews/exp-logger')()

logger.info("Hello world")

/* 
-- expected output
[15:19:13.240] INFO: Hello world
*/

Format the log object

To change the shape of the log object to match gcp error-reporting structure or similiar, use formatLog

const expLogger = require('@bonniernews/exp-logger');

const logger = expLogger({
    formatLog: (obj) => {
        if (!obj.err) {
           return obj;
        }
        const stackTrace = obj.err?.stack;
        return {
            ...obj,
            ...(stackTrace && { stack_trace: stackTrace }),
        };
    }
);

logger.error(new Error('Something wrong'));