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

node-diagnostics

v0.0.4

Published

Logging and Timer to perform some basic profiling and diagnostics

Downloads

4

Readme

Diagnostic logging and basic profiling using Timers

This module wrap the node.js util.log funciton with some basic level filtering and prefix the message with the process.pid and module name provided.

It also has a Timer functionnality to profile/measure the elapsed time in certain part of your code.

#LICENSE:

This module is licensed under the Apache License v2.0

Installation

npm install node-diagnostics

Include this as a module in your own project

// All diagnostics logs will be prefixed with 'MyModuleName'
var diag = require('node-diagnostics')('MyModuleName');

// Start a timer to display the elapsed time of this section of code.
var timer = diag.startTimer();

// Set the diagnostic level to INFO. Make sure that you reassign the diag
// object with the result of setLevel if you want to be able to use the
// 'diag.level' in you if condition, otherwise it will have the default
// value of 'error'!
diag = diag.setLevel(diag.info);

diag.log(diag.finest, 'FINEST|Will not be shown, but the string concatenation'
                      + ' will still be done and the method called, it is'
                      + ' slower than the next invocation.');
if (diag.level >= diag.finest) diag.log(diag.finest, 'FINEST|Will not be shown'
                      + ' but no method invocation and no string concatenation.'
                      + ' this is the prefered way');

if (diag.level >= diag.info)   diag.log(diag.info, 'INFO|Will be shown!');
diag.log(diag.info, 'INFO|Will be shown!');


diag.log(diag.info, 'test ran in ' + timer.stop().format());