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

js-console-logging

v0.1.1

Published

A wrapper around console (debug, info, etc.) to have control of log levels.

Readme

Transparent Logger

This logger binds console logging functions to produce log output with consistent code references in developer console.

It also supports log levels and a log hierarchy, such that you can control levels in the hierarchy.

A simple logger:

  logger = require('js-logging')
  logger.setLevel('debug')

I developed this logger for atom packages and tests run in atom suite, so there is some specific support for this:

  logger = require('js-logging')
  # logger starts per default in logging only errors
  logger.setSpecLevel('debug')
  log.debug 'this message appears only in atom spec test mode'

You have following logging functions:

  logger = require('js-loggiing')
  fooLogger = logger.getLogger('foo')
  barLogger = logger.getLogger('foo.bar')
  oneMoreBarLogger = fooLogger.getLogger('bar')
  barLogger is oneMoreBarLogger # is true
  fooLogger.setLevel('info')
  barLogger.level # is also 'info' now
  barLogger.setLevel 'silent' # no logging at all

  logger.debug "debug message"
  logger.trace "stack trace at this position"
  logger.log   "a log message"
  logger.info  "information"
  logger.warn  "warning"
  logger.error "error"

Log levels are configured as follows:

| level | value | |--------|-------| | silent | 0 | | error | 1 | | warn | 2 | | info | 3 | | log | 4 | | trace | 5 | | debug | 6 |