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 🙏

© 2026 – Pkg Stats / Ryan Hefner

bookrc

v0.0.1

Published

automatic config loading for the book logging framework

Readme

bookrc Build Status

automatically load book logging configuration from your environment or valid bookrc.js files.

bookrc allows you to configure your book logging in one place for your project. It follows a simple lookup pattern and returns either your bookrc.js file or the default book module.

use

Lets say we have application code which wants to do some logging and we want the logging to be sent to various locations and processed through the book middleware stack.

In the root of our app, we would create a bookrc.js file which can setup additional middleware and logging features.

var log = require('book').default();
var raven = require('book-raven');
var git = require('book-git');

// we want to add a .commit field to our log entry with the git commit hash
log.use(git(__dirname));

// we want to log errors to raven
log.use(raven(process.env.SENTRY_DSN));

// now we just expose the logging object
module.exports = log;

Now we just require('bookrc') and use it like we used book before. Except now our logs will run through our middleware stack and be tagged with our commit id and send to sentry for alerting.

Our app code does not have to change much at all. Simply update require('book') to require('bookrc') and you are set.

// instead of require('book'), use require('bookrc');
var log = require('bookrc');

// now you can just log as before, no other changes
log.info('foo');
log.error('bar');

BOOK_RC env variable

If bookrc.js does not exist in the root of your project, or bookrc cannot find it. You can specify it manually using the BOOK_RC environment variable. Set the variable to the absolute location of the bookrc.js file and bookrc will load that instead of searching.

install

Bookrc does not depend on book and vice versa. You must install both to have logging functionality. Bookrc is simply a dynamic loader for the bookrc.js file in your project.

npm install bookrc
npm install book