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

historical-console

v0.0.1

Published

Keep a history of your javascript's console.* calls:

Downloads

7

Readme

historicalConsole.js

Keep a history of your javascript's console.* calls:

historicalConsole(function(console) {
  console.debug(foo, 'asdf');
  (function someName() {
    console.info('function name test');
  })();
})();

The resulting console.history:

[
 ['debug', {fooObj: 'O'}, 'asdf', 'caller:function(console) { console.debug(foo, '],
 ['info' , 'function name test' , 'caller:someName']
]

Recent history can then be bundled with error reports. Generating this console.history array is the point of this library.

Don't care about caller:names? console.options.addCaller(false)

Function naming:

If you don't name your functions (or use coffeescript), I include the first 40 characters of the function's .toString value. Change the 40 char snippit length with: console.options.functionSnippetLength(30)

Track calls to alert:

historicalConsole(function(console, alert) {

Globally intercept console calls:

historicalConsole(function(console) {
  window.console = console;
});

caller:null means a function was called at the global scope (no function called it)

historicalConsole.noConflict

To play it super safe:

myModule.historicalConsole = historicalConsole.noConflict();

Integrate with other things:

Override console.history.add with your own callback! This function is called whenever any console.* method is called. For example, when you call console.log('foo'), console.history.add will be called with this one argument:

['log', 'foo', 'caller:someFunc']

Maybe you want to receive all entries and do something interesting wtih them:

historicalConsole(function(console) {
  console.history.add = function consoleHistoryCallback(logStatement) {
    //~whateva you want bro~ 
  };
})();

The console.history array will not exceed 200 entries, or whatever maximum you set:

console.options.consoleHistoryMaxLength(100);

TODO: console.dir, profile, and profileEnd

Other functions are exposed on the log object for your flexibility, if you want to understand and use these, read over the fully commented source below