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

outrider

v2.0.0

Published

Package aware bunyan logger

Downloads

9

Readme

outrider

npm install outrider

outrider logger is wrapper over bunyan to allow for easy log management inside of projects that consist of several in house libraries. This library makes sure that logs both end up in the right place and are delivered with necessary meta information.

Behavior

The goal of outrider is to make logging with a large number of libraries that are being used in many different situations easy. Lets consider a project with the following dependency structure:

[email protected]
└─┬ [email protected]
  └── [email protected]

With outrider this project will log out to a file called foo.log and will name space foo, bar, and baz as [email protected], [email protected], and [email protected]. There will also be a foo-error.log file for error level messages. The log file will have all levels of messages (eg trace and higher) and anything info and higher will be logged to stdout.

Lets dig a little deeper, lets say that we now require foo in a project called main.

[email protected]
└─┬ [email protected][email protected]
  └── ...

Now outrider will log to main.log with the same name spacing structure as before. Additionally, the log file will differentiate between [email protected] and bar1.2.0 making it easy to see errant behavior between different versions of libraries.

By using outrider it is easy to manage log files as your libraries and services grow in complexity.

Caution

outrider will only log to a file if there is a main module for the process. If there is no main module (eg a package is included from the node REPL) then outrider will only log to stdout.

Usage

outrider is easy to set up:

// preferred way:
var log = require('outrider')(require('./package.json'));
// or
log = require('outrider')(name, version);

The log variable is just an instance of the bunyan logger, so feel free to use it as you would any bunyan instance.

log.error();
log.warn();
log.info();
log.debug();
log.trace();

and now your logs are ready to go!

Configuration

outrider will look for process.env.NODE_LOG_LOCATION as a directory to write log files to. If this is not found then outrider will default to ./.

License

MIT