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

stack-logger

v1.1.1

Published

Easily build up a log trail while writing modules.

Downloads

4

Readme

Stack Logger

Build Status

Easily build up a log trail while writing modules.

Usage Notes

// There are 4 StackLogger types, corresponding to console methods
StackLogger.Error
StackLogger.Warn
StackLogger.Info
StackLogger.Log

// These are aliases of the generic StackLogger
StackLogger.Error()
// is the same as
StackLogger('error')

// A StackLogger can be initialized with its topmost message
var _error = StackLogger.Error('My Error Generating Class has an Error:')

// StackLogger combines stacked messages with '\n\t'
_error.log('Bad input.') // equiv.: console.error('My Error Generating Class has an Error:\n\tBad input.')

// StackLogger is meant to be used to build up a trail of information while writing modules
// This helps narrow down where errors are coming from, especially in certain contexts (like async
//   callbacks) where stack traces aren't always that helpful
function method () {
  // StackLogger.push and StackLogger.pop are immutable updates, so _error is unaltered.
  var _methodError = _error.push('Method: [MyErrorGeneratingClass::method]');

  // some time later...
  _methodError.log('That\'s no good. Stop that.');
  // console error output:
  //    'My Error Generating Class has an Error:'
  //    '  Method: [MyErrorGeneratingClass::method]'
  //    '  That\'s no good. Stop that.'

  _error.log('I am still here.')
  // console error output:
  //    'My Error Generating Class has an Error:'
  //    '  I am still here.'

  // Let's try using StackLogger in some async code. We'll need this function:
  function failCallback (logger) {
    return function (response) {
      logger.log('The asynchronous request failed with error code: ' + response.status)
    }
  }

  // Now let's send a GET request from the method we're currently in:
  $.get('my-api/v1.0.3/endpoint')
  .then(function (data) {
    // ...
  })
  .catch(failCallback(_methodError))
  // Now if the GET request fails, our console error will tell use that we were in this method
}

// StackLogger also has #pop()
var _error = _methodError.pop(); // => StackLogger

_error.log('Hello!') // console error output: 'My Error Generating Class has an Error:\n\tHello!'

_error = _error.pop()    // => StackLogger

_error.log('Hello!') // consoler error output: 'Hello!'