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

debug-pest

v1.0.1

Published

logging utilities over visionmedia's debug for javascript

Downloads

3

Readme

debug-pest

Commonly useful logging extensions over visionmedia's debug Wraps over debug, instead of modifying anything.

Features

  1. Log levels - Drop in replacement for console, mostly (ie implements log, warn & error)
  2. Easy child instances
  3. Each log-level of a logger (parent or child), is its own debug instance.

Note

  1. debug-pest is a extremely light wrapper over 'debug', and is purposely setup to use 'debug' as an optional dependency - to reduce weight where debug might only be needed for testing (for eg). If 'debug' is not provided, it will disable (.enable = false) the loggers silently, without affecting your code.

  2. This implementation deviates slightly from the original convention set by debug.

The topmost namespace is not your app's name, but the log level. This is to allow configs like :

  • ('errors:* , -logs:* , -warnings:* ') : Show all errors, but suppress logs & warnings, irrespective of module

Usage

const debug = require('debug');
debug.enable('*');
const debug-pest = require('debug-pest')(debug);

const parent = new debug-pest('Parent');

/* Loggers are enabled only when debug is provided.

Using "parent.enabled &&" as below is not necessary, but may be more efficient  when the loggers are disabled, than simply calling .log(), .warn(), .error() as is - because it avoids those function calls entirely.

*/
parent.enabled && parent.log('Hello. This is a log from parent');
parent.enabled && parent.warn('Hello. this is a warning from parent');
parent.enabled && parent.error('Hello. this is an error from parent');

const child = parent.child('child1');
child.enabled && child.log('Hello. This is a log from child1');

Roadmap

  • Output to file(s), paired with a web based filtered log viewer.