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

bunyan-hub-logger

v1.2.1

Published

log to bunyan-hub

Downloads

35

Readme

bunyan-hub-logger

This module is a high level module to be used with bunyan-hub to play as a drop in replacement to tj's debug module and serve as a logging module for your iojs/node.js project.

install

You should have bunyan-hub installed globally first, then start it.

npm i -g bunyan-hub
bunyanhub start

then install bunyan-hub-logger in you iojs project (or node.js project, not tested) locally

npm i --save bunyan-hub-logger

usage

logger

var logger = require('bunyan-hub-logger');

var log = logger('web')
// log object here is a bunyan logger with the name 'web'
log.trace('log trace')
log.debug({req: req}, 'debug http request');

/* logger options
logger(object opts) or logger(string opts)
logger({
    name: 'api', // currently debugging/logging module of your app/project
    app: 'project-a', // your app/project name
    serializers: {}, // bunyan serializers, defaults to a modified bunyan.stdSerializers which append a `uuid.v4()` to req.req_id and res.req.req_id for req and res
    streams: [], // default is using bunyan-pub-stream to send logs to local bunyan-hub, you can add more bunyan writable stream here.
});
if opts object is string it will be convert to { name: opts }
*/

You need specified app name in app and module name in name since bunyan-hub is serving as a centralized log aggregator, it will recieve logs from multiple running apps. name is like namespace in tj's debug module, and different app may use the same module name for the same or different module (e.g. request namespace in frontend app and backend app...)

debug (from tj) replacement

require('bunyan-hub-logger/replaceDebug')(appname);

for example you drop a line require('bunyan-hub-logger/replaceDebug')('web-a'); in your web-a app, and it using superagent as http requesting module, then you will see logging records {"name": "superagent", "app": "web-a", ... } in bunyan-web or bunyan-sub, since superagent using debug module under namespace "superagent"

console replacement

require('bunyan-hub-logger/replaceDebug')(appname);

like replaceDebug, this will replace console object to send log to bunyan-hub.

license

MIT