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

console-filterify

v1.0.0

Published

Browserify transform that wraps all `console.*` calls in a filtering function that can be changed live directly in the browser.

Downloads

2

Readme

console-filterify

Browserify transform that wraps all console.* calls in a filtering function that can be changed live directly in the browser.

If console.filterify is defined, it will be called with the console method (such as log, warn, error, dir) as first argument and the original console arguments as an array as the second argument.

This function is assumed to return either an array to log - possibly with manipulated values - or undefined to ignore logging this line at all.

If console.filterify does not exist, the wrapper logs as usual.

Purpose

The usual approach to filtering or coloring or decorating loggers are to have a wrapping library, which usually loses important information such as line and file name. This is not necessarily that much better, but offers a way to keep that kind of information as well as filter and/or manipulate the logging data dynamically on the way.

Examples

/**
* @param {string} level The log level such as log, warn error etc
* @param {array} args   Array of original arguments
* @return {array} of arguments, possibly modified, or undefined to silence this log line 
*/
console.filterify = function(level, args) {
    if(['warn', 'error'].indexOf(level) > -1) {
        return args;
    }
    return undefined;
}
// Add red CSS color to error log
console.filterify = function(level, args) {
    if(level === 'error' && args.length > 0) {
        args[0] = '%c' + args[0];
        args.splice(1, 0, 'color:red');
    }
    return args;    
}