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

process-winston

v0.0.0

Published

Simplifies sharing a process wide Winston.

Downloads

5

Readme

process-winston Build Status

process-winston allows the configuration of a process wide winston instance that can be used by all modules. This allows the main module to configure a winston instance and all other modules to share one configuration.

Why?

Because modules want to log stuff.

How?

Setup process-winston as soon as possible in your main application like so:

var logger = require('process-winston').init(require('winston', {
  console: {
    level: 'warn',
    colorize: 'true'
  }
})).add('mylogger', {console: {level: 'info'}});

The second argument to process-winston's init method is the default logging information to apply to all loggers. All default options are deep-extended into the options passed when adding a logger. Modules find their loggers like so:

var log = require('process-winston').get('modulename');

and then they just use the logger.

Now if you want to see lots of logging from the module named modulename you'd change the initialization section in the main application to be this:

var pwinston = require('process-winston').init(require('winston', {
  console: {
    level: 'warn',
    colorize: 'true'
  }
})),
    logger = pwinston.add('mylogger', {console: {level: 'info''}});
pwinston.add('modulename', {console: {level: 'silly'}});