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 🙏

© 2026 – Pkg Stats / Ryan Hefner

commentlogger

v1.0.2

Published

logging module for nodejs using comments

Readme

commentlogger

commentlogger enables developers to move their debugging console.log() out of their code and into the comments, resulting in a cleaner code.

installing

install using npm i commentlogger

using

const logger = require('commentlogger');
logger.watch(() => {
    module content ...
})();

wherever a log is required, add a // , then add log(message, env)

The following logs sum when NODE_ENV is set to dev:

const sum = 3 + 2; // log(sum, dev)

This one will run if the environment is set to prod:

const result = calculateSomething(); // log(result, prod)

Multiple env can be set:

const result = calculateSomething(); // log(result, dev, test)

if env is not provided, logging will be done regardless of NODE_ENV value;

const sum = 3 + 2; // log(sum)

It is not limited to logging variables. You can put messages to be logged

throw new Error("something went wrong"); // log("an error occurred");

defining custom logging behavior

By default, console.log is used by the library. But a custom logic can be set as the second argument of watch() function

const logger = require('commentlogger');
logger.watch(() => {
    module content ...
}, (msg) => someCustomFunction(msg))();

The example below writes logs to a file:

const logger = require("commentlogger");
const fs = require("fs");

function writeToFile(msg) {
    fs.appendFile("file.log", msg.toString() + "\n", (err) => {
        if (err) {
          console.error(err);
        }
    });
}

logger.watch(() => {
    module content....
},
    (msg) => writeToFile(msg)
)();