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

log-comments

v0.2.0

Published

Convert JavaScript comments in log

Readme

log-comments

Convert JavaScript comments in logs, warnings or errors

Getting Started

Install the module with: npm install log-comments

Documentation

This tool should help in some rare situations, where you want your app to log for debugging purpose, but only in testing or in production environment, so you don't want be distracted by a bloat of logs when you are developing. Just put one of these three

  • <-{l}
  • <-{w}
  • <-{e}

strings at the end of your comment and the comment will be wrapped respectively with console.log(), console.warn(), console.error();

Options

--in-place, -i: overwrite existing file with the new one
--directory, -d: specify a directory, all .js files inside directory will be parsed and elaborated
--help, -h: print help

Examples

###code // This will be a log <-{l}
// This will be a warn <-{w}
// This will be an error <-{e}

cli

log-comments [OPTIONS] [FILE]

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using grunt.

Release History

(Nothing yet)

License

Copyright (c) 2013 Manuel Bitto
Licensed under the MIT license.