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

js-log

v0.4.1

Published

Configurable as winston, tunable as debug()

Downloads

9

Readme

Simple & configurable logger

Usage:

var log = require('js-log')();

log.info("Hi everyone!");

log is a winston-based logger with usual methods.

By default it prints all messages except log.debug() and prepends them with module filename and directory.

Logging methods:

  • log.debug(...)
  • log.info(...)
  • log.error(...)

The signature is like console.log.

Additionally:

  • log.debugOn() -- enable debug for this very logger

Options:

var log = require('js-log')({
  module: <module object to log for>, by default - the requiring module,
  getShowPath: <function which returns label for module>
  getLogLevel: <function which returns log level (error/info/debug) for module>,
  getTransports: <function which returns transports for (logLevel, label)>
});

All options are optional.

DEBUG

There're two ways to enable debugging.

  1. Call log.debugOn() in the code
  2. Use DEBUG environment variable

Turn on all debugging:

DEBUG=* node app

DEBUG can be either '*' or a file mask to debug, in the same format as https://github.com/visionmedia/debug.

Examples:

// all files from the models/* folder (from project root)
DEBUG=models/* node app

// all files from models/* and lib/*
DEBUG=models/*,lib/* node app

// all files from models/* except models/user
DEBUG=-models/user,models/* node app

It's quite important that DEBUG is also used on many frameworks.

DEBUG=* will enable all debug for both your loggers and internal debugging of frameworks.

Sometimes it really helps.