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

loggify

v0.1.0

Published

wraps functions, constructors and util object style collections of functions in entrance and exit logs using a logger provided by the consumer

Downloads

4

Readme

Loggify!

This is a small module for adding logging to things without cluttering function definitions with log statements. It is my firm belief that logging and logic should not be mixed, and that separating them will improve readability.

Usage

Note: loggify is not a logging module, it is just a module for adding logging to functions, assuming you already have some kind of logger. You could be using Minilog, plain old console or something else, loggify does not care.

// init loggify
var loggify = require('loggify')(logger); // some obj, hopefully with an 'info'
function

loggify(objectOrFunction[, name, level])

You can loggify a single function, a collection of functions which are keys on an object, or even a constructor along with functions on the prototype. The name and level parameters are optional. The name will default to objectOrFunction.name if it exists or just an empty string. The level defaults to info, this needs to be a valid member function on the logger object you initially passed to loggify.

var mySuperFunc = function(a,b) {
  return a + b;
}

mySuperFunc = loggify(mySuperFunc, 'mySuperFunc', 'warn');

mySuperFunc(1,3);  // logs function entry + arguments
                   // also logs function exit + return val

var bagOFunctions = {
  'add': function(a,b){return a+b;},
  'multiply': function(a,b){return a*b;}
};

bagOFunctions = loggify(bagOFunctions, 'stuff');
            // overwrites add and multiply with loggified versions
            // defaults to 'info' log level
            // will log 'stuff.add', because that's the name supplied

var Car = function(x,y) {
  this.x = x; this.y = y;
};

Car.prototype.drive = function(distance){
  this.x = this.x + distance;
  return [this.x, this.y];
};

Car = loggify(Car, 'Car');
           // loggify the constructor and prototype functions