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

mydbg

v1.0.2

Published

Simple wrapper of debug module with debug level control.

Downloads

3

Readme

mydbg

Simple wrapper of nodejs debug module with debug level control.

Install

npm install mydbg

Usage


const dbg = require('mydbg')('app');

dbg.info('app starting...');

try {
    ...
}catch(ex){
    dbg.err(ex.message);
}

Levels

There are 5 levels of debug messages supported:

  • trace: detailed messages for development

  • info: generic information messages

  • warn: something abnormal detected, but app can still run

  • err: error detected, but app can still run

  • fatal: error detected, app must terminate

The importance of levels are sorted as following:

trace < info < warn < err < fatal

Output Control

The output of debug messages can be controlled by its level in DEBUG environment variable

DEBUG=app.warn,app.err,app.fatal

or simply use '+' to specify that all messages of the same or high levers are included:

DEBUG=app.warn+

To enable warn messages of all app modules:

DEBUG=*.warn

To enable messages starts from warn level:

DEBUG=*.warn+

To enable messages for multiple moduels:

DEBUG=app.warn+,srv.err+,-ui.*

Please refer to debug module for Wildcards

Methods

  • trace() / info() / warn() / err() / fatal()

They are message output api for each debug level. please refer to debug module for Formatters


const dbg = require('mydbg')('srv');

dbg.trace('server starts');
  • throw_error(message | error)

outputs the message as err level and throw an Error instance.


if(something_bad_detected){
    dbg.throw_error('critial error!');
}

try {
    ...
}catch(ex){
    dbg.throw_error(ex);
}