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-blame

v1.1.3

Published

It highlights and helps to find forgotten console.log calls in runtime

Downloads

21

Readme

console-blame

NPM Version Build Status Coverage Status Dependency Status

It highlights and helps to find forgotten console.log calls in runtime. Live example

Installation

console-blame can be installed using npm:

npm install console-blame --save-dev

Interface

  • ConsoleBlame(Object consoleObject, String[] trapsList)
  • ConsoleBlame(Object consoleObject)
  • ConsoleBlame(String[] trapsList)
  • ConsoleBlame()
  • ConsoleBlame#configure(Object options) see Configuration options
  • ConsoleBlame#restore() releases all trapped methods
  • ConsoleBlame#trap(String[] ...methods) traps all listed methods
  • ConsoleBlame#trap() traps all available methods

Configuration options

Can be configured, using require('console-blame').configure({ ... })

  • pathFormat format of file name, line and column. default: '%s:%d:%d'
  • lineFormat format of code line. default: '%d | %s'
  • contextSize number of lines before and after target line. default: 3
  • sources print source code? default: true

Example

Trap all methods of console

require('console-blame')();

console.log(123); // Will print debug message
console.error(123); // Will print debug message

Trap only console.log

require('console-blame')(['log']);

console.log(123); // Will print debug message

Trap only log and error of specific console object

require('console-blame')(console, ['log', 'error']);

console.log(123); // Will print debug message

Trap all methods and change size of context and line format

require('console-blame')().configure({
   contextSize: 5,
   lineFormat: '%d\t%s'
});

console.log(123);

Restore traps

var blame = require('console-blame')();
console.log(123); // Will print debug message
blame.restore();
console.log(123); // Will NOT print debug message
blame.trap();
console.log(123); // Will print debug message

Output example

A log message
/home/username/projects/console-blame/lib/index.js:174:9
 169 | attachTrapsTo(console).configure({
 170 |   contextSize: 5,
 171 |   lineFormat: '%d\t%s'
 172 | });
 173 |
 174 | console.log('A log message'); // <<< This line will be highlighted
 175 |