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

@luispablo/multilog

v1.2.0

Published

Simple wrapper for multiple loggers. Initially graylog and console.

Downloads

2

Readme

multilog

Simple wrapper for multiple loggers. Initially graylog and console.

Good news! Now support for Node 0.10

Installation

npm install --save @luispablo/multilog

Usage

First, get from anywhere you want some JSON with the properties. Such JSON must be an array with objects, with each object being a logger configuration.

For example, to get one console logger and one GrayLog logger use this:

const properties = [
	{name: 'console', level: 'DEBUG'},
	{
		name: 'gelf',
		level: 'WARN',
		config: {
			fields: {facility: "example", owner: "Tom (a cat)"}, // optional; default fields for all messages
			filter: [], // optional; filters to discard a message
			broadcast: [], // optional; listeners of a message
			adapterName: 'udp', // optional; currently supported "udp" and "tcp"; default: udp
			adapterOptions: {
				protocol: 'udp4', // udp only; optional; udp adapter: udp4, udp6; default: udp4
				family: 4, // tcp only; optional; version of IP stack; default: 4
				host: '127.0.0.1', // optional; default: udp4
				port: 12201 // optional; default: 12201
			}
		}
	}
]

Logging levels

So far, we have INFO, ERROR, WARN and DEBUG. And they work as you would expect them to. You must specify the level in each logger. In every single logger? YES, deal with it.

Then, create a MultiLog object:

const MultiLog = require("@luispablo/multilog");

...

const log = MultiLog(properties);

and you're ready to go!

log.info("This is an info message");

...
const error = {code: 5, message: "Error message"}; // This can be anything you want
log.error(error);

and that's it, for the moment.

Credits

@luispablo