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

v0.0.1

Published

Simple performance.now shim with automatic logging

Downloads

1

Readme

console-performance

Simple performance.now shim with automatic logging.

Screenshot

How to use

The syntax is very simpel:

consolePerformance.start(tag, text);
// Code
consolePerformance.end(tag, text);

The tag is what connects the start and end and the text (optional, default is the tag) is what will be logged in the console. You can use substitution strings to get the tag name and the time (available in the end method) with %s and %d Complete example:

consolePerformance.start('replace', 'Starting test %s');
'Hello world'.replace('world', 'stockholm');
consolePerformance.end('replace', 'Test %s executed in %dms');

Look in the example.html for examples.

Extra

To use clean mode (no coloring and no tag replacements) set a third parameter to true.

Tips

Logs is not nice in production, therefor it can be a good idea to disable them. I recommend setting a global variable called DEBUG when working in the browser and in node use an environment variable. Having DEBUG=false will automatically disable the performance stuff from this library. If you use uglify you can also add --define DEBUG=false to your build to remove the blocks completely from the code.

It can also be a good idea to turn of console.log completely. Again, if using uglify you can add drop_console to your compressor. Otherwise you can just set console.log to an empty function:

if ((typeof DEBUG === 'undefined' || !DEBUG) && typeof console !== 'undefined') {
	console.log = function () {};
}