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

@wmhilton/log

v1.1.0

Published

A console.log replacement

Downloads

2

Readme

log

This may not be everyone's cup o' tea, but this is the library I've written for console.log-style debugging.

Improvements over console.log

  • Timestamps (with optional timezone configuration)
  • Filename and line number of the caller
    • CoffeeScript files have correct line numbers too (using coffee-errors)
  • Colored log levels (using chalk)
  • Objects and arrays are pretty-printed using JSON.stringify instead of [object Object]
  • Error objects are pretty printed (using pretty-error)
  • Smart truncation of long strings and arrays
  • 'quiet' option to quickly turn logging off/on
  • 'filename' option to write directly to a file instead of stdout
  • EventEmitter interface so you can listen for log messages (say, to copy all messages to the Captain's log, or perform evasive manuvers on 'error' and 'fatal' messages)

Usage

// A single, global log object. Don't call with "new".
log = require('log')

// Calling setup is optional.
log.setup({
  filename: String   // optional, if specified writes to file instead of stdout (has precedence over `stdout`)
  quiet: Bool        // optional, default false, if true turns disables output but still triggers events
  timezone: String   // optional, defaults to "America/New_York"
  colors: Bool       // optional, default is chalk's autodetect behavior
  stdout: Stream     // optional, if specified log writes to a Writable Stream instead of process.stdout (since v1.1.0)
  cutoffLength: Number // optional, default 250, the length to truncate long strings (since v1.1.0)
})

// Available log methods
log.log(args...)
log.debug(args...)
log.info(args...)
log.warn(args...)
log.err(args...)
log.fatal(args...)

// Event listener example(s)
log.on('err', function(e) {
  // Print errors to stderr
  process.stderr.write('ERROR: ' + e.message)
})
log.once('fatal', function(e) {
  // Take 'fatal' errors literally
  process.exit(1)
})

Example output

Screenshot of the colorized log levels, using Solarized terminal color scheme:

capture

Example of a pretty error stack:

image