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

@kth/log

v4.0.7

Published

Logging module for Node.js applications.

Downloads

3,361

Readme

@kth/log

Logging module for Node.js applications.

Usage

The package will respect NODE_ENV and output serialized JSON in production and use ordinary output for development.

The package uses bunyan.stdSerializers.err for err and provides serializers for req and res objects. Only subset of fields are displayed by these serializers.

In your application

const log = require('@kth/log')

// in application setup, see full options below
log.init({
  name: 'node-app',
  level: 'warn',
})

// log usage
log.info('hello from info, log level usually used in setup')
log.warn('error that code handled and can recover from')
log.error({ err: err }, 'error that should be fixed in code')
log.fatal('a really bad error that will crash the application')
log.debug({ req: req, res: res }, 'log a request and response, basic dev log')
log.trace('granular logging, rarely used')

// child logger
// add custom values to all of the logs
const myLog = log.child({ custom: 'value' })
myLog.info('hello')

Options

log.init({
  // name of the logger, usually the same as application name, default is 'node-log'
  name: 'node-app',

  // If developement or test, the output is sent to stdout (console) using Bunyan-format 'short', default value is retrieved from process.env.NODE_ENV
  env: 'development',

  // default logging level is INFO
  level: 'debug',

  // Provide a custom serializer if necessary, default serializer for err, req and res are included in the package.
  serializers: {
    err: customSerializer,
  },
})