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

layer-logging

v0.0.4

Published

Provides logging

Downloads

14

Readme

layer-logging

Build Status Coverage Status

Getting Started in 1 Minute

  1. Provides logging levels:
    • ERROR
    • WARN
    • INFO
    • DEBUG
    • TRACE
    • SILENT
  2. You can't set the level to SILENT (It's special).
  3. To use the logger, you instantiate it preferably providing at least one key.
  4. You can use the static properties filterIn and filterOut to override the current level.
  5. If a key is specified in filterIn the log will go out no matter the level.
  6. Same with filterOut, but if a key is specified on both in and out, it will be skipped.
  7. The only way to echo SILENT logs, is by including the key in filterIn

Examples

Create Logger and Use It

const logger = new Logger('app');
logger.trace("Hello", "World");
// Prints:
// [2025-01-01T18:04:38.233Z] [INFO]   [APP] Hello World

Log at Different Levels

const logger = new Logger('app');
Logger.setLevel('INFO');
logger.error('Something happened');         // Will go out
logger.trace('Small bit');                  // Won't go out
logger.silent('Specific debug');            // Will never go out if 'app' is not on Logger.filterIn