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

4front-logger

v1.0.1

Published

Bunyan based logger for 4front

Downloads

5

Readme

4front-logger

NPM Version NPM Downloads Build Status Test Coverage

http://4front.io

Default logger for the 4front multi-tenant web app platform. Learn more at: 4front.io

Internally bunyan is used for JSON logging. In accordance with 12 factor app practices, by default errors and warnings are are streamed to process.stderr and info level messages are streamed to process.stdout. This behavior can be overridden via the options as described below. Recommended practice is to setup a log sink external to the node app which sends log events from all servers in a cluster to a centralized logging system such as Splunk, Loggly, or Papertrail.

Installation

npm install 4front-logger

Usage

var app = express();
var log = require('4front-logger')({
  loggerName: "4front-logger"
});

// Register the logger with 4front
app.settings.logger = log;

Options

loggerName The name of the logger which will be added by

errStream The stream where error level messages are written. Defaults to process.stderr.

warnStream The stream where warn level messages are written. Defaults to process.stderr.

infoStream The stream where info level messages are written. Defaults to process.stdout.

ignoreErrorStatus Array of http err.status codes to ignore. Defaults to [404].

API

Any of the methods error, warn, or info can be called in all the ways that bunyan supports:

log.info("informational message");
log.info({foo: 'bar'}, 'hi');

Additionally the error function includes a special overload that accepts an Error object and an Express req object. The logger will ensure that all the error detail along with additional contextual information found on the req are captured in the log entry. 4front uses this method in error handling middleware:

app.use(function(err, req, res, next) {
	log.error(err, req);
	next();
});

Running Tests

npm test

License

Licensed under the Apache License, Version 2.0. See the top-level file LICENSE.txt and (http://www.apache.org/licenses/LICENSE-2.0).