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

@wiredcraft/bunyan-logger-factory

v1.3.1

Published

From time to time, I found I have to create [Bunyan](https://www.npmjs.com/package/bunyan) instance with different streams(stdout/file/syslog) for different environments.

Downloads

50

Readme

Why I create this libray

From time to time, I found I have to create Bunyan instance with different streams(stdout/file/syslog) for different environments.

How to use

const loggerFactory = require('bunyan-logger-factory');

const myLogger = loggerFactory.init({
  logName: 'my-logger-name',
  logStreams: [
    {
      streamType: process.env.LOGSTREAM,
      streamHost: process.env.LOGHOST,
      streamPort: process.env.LOGPORT,
      streamProto: process.env.LOGPROTO,
    }
  ],
});

Advanced usage

You can also set the transformation to the logger.

constant

const loggerFactory = require('bunyan-logger-factory');

const myLogger = loggerFactory.init({
  logName: 'my-logger-name',
  logStreams: [
    {
      streamType: process.env.LOGSTREAM,
      streamHost: process.env.LOGHOST,
      streamPort: process.env.LOGPORT,
      streamProto: process.env.LOGPROTO,
    }
  ],
  transform: [
    {
      constant: {
        ipsum: 'xxx',
      },
    },
  ],
});

This will add ipsum: xxx to each log created.

clone

const loggerFactory = require('bunyan-logger-factory');

const myLogger = loggerFactory.init({
  logName: 'my-logger-name',
  logStreams: [
    {
      streamType: process.env.LOGSTREAM,
      streamHost: process.env.LOGHOST,
      streamPort: process.env.LOGPORT,
      streamProto: process.env.LOGPROTO,
    }
  ],
  transform: [
    {
      clone: {
        msg: 'message',
        time: 'timestamp',
      },
    },
  ],
});

This will generate two extra fields message and timestamp which have exact same value as msg and `time**.

map

const loggerFactory = require('bunyan-logger-factory');
const fn = (v) => {return v + v;};

const myLogger = loggerFactory.init({
  logName: 'my-logger-name',
  logStreams: [
    {
      streamType: process.env.LOGSTREAM,
      streamHost: process.env.LOGHOST,
      streamPort: process.env.LOGPORT,
      streamProto: process.env.LOGPROTO,
    }
  ],
  transform: [
    {
      map: {
        foo: fn,
      },
    },
  ],
});

This will populate the value of foo by calling the fn function.

avoidChildTransform

By default, the logger.child will inherit the transformation you set on the parent if there is a tranform in the init function, you can set avoidChildTransform to true to prevent that behavior.

const logger = loggerFactory.init({
  logName: 'test-logger',
  logStreams: [
    {
      streamType: 'FILE',
      streamPath: filePath,
    }
  ],
  avoidChildTransform: true, // the transform only applies on the current logger instance.
  transform: [
    {
      constant: {
        ipsum: 'xxx',
      },
    },
  ],
});

multi streams

It's possible to add multiple stream configs in logStreams.

const logger = loggerFactory.init({
  logName: 'multiStream',
  logStreams: [
    {
      streamType: 'stdout'
    }, 
    {
      streamType: 'syslog',
      streamHost: 'localhost',
      streamPort: 514,
      streamProto: 'tcp'
    }
  ]
});

License

MIT