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

debugged

v0.1.0

Published

Lightweight wrapper for the debug module

Downloads

11

Readme

8888888b.           888                                               888
888  "Y88b          888                                               888
888    888          888                                               888
888    888  .d88b.  88888b.  888  888  .d88b.   .d88b.   .d88b.   .d88888
888    888 d8P  Y8b 888 "88b 888  888 d88P"88b d88P"88b d8P  Y8b d88" 888
888    888 88888888 888  888 888  888 888  888 888  888 88888888 888  888
888  .d88P Y8b.     888 d88P Y88b 888 Y88b 888 Y88b 888 Y8b.     Y88b 888
8888888P"   "Y8888  88888P"   "Y88888  "Y88888  "Y88888  "Y8888   "Y88888
                                           888      888
                                      Y8b d88P Y8b d88P
                                       "Y88P"   "Y88P"

Debugged is a lightweight wrapper for the debug module.

Build Status Peer Dependency Status Dev Dependency Status License Release

Install

Install using npm:

$ npm install --save debugged

You'll need to have at least Node.js 4 or newer and debug@^2 is required as a peer dependency.

API

The API is really just a wrapper around the debug module that follows an Object-oriented Programming (OOP) pattern. The main purpose of it is not really for the API design, but for a shared bucket of debug instances per namespace whose enabled status is automatically refreshed.

The only real difference is how you create debug instances and how you log messages:

const Debugged = require('debugged');

const debug = Debugged.create('app');
debug === Debugged.create('app');
//=> true
debug === Debugged.create('app:example');
//=> false

debug.log('Started %d', process.uptime());

debug.enabled;
//=> false

Debugged.enable('app');

debug.enabled;
//=> true

Debugged.disable();

debug.enabled;
//=> false

Bugs

If you have any problems with Debugged or would like to see changes currently in development you can do so here.

Contributors

If you want to contribute, you're a legend! Information on how you can do so can be found in CONTRIBUTING.md. We want your suggestions and pull requests!

A list of Debugged contributors can be found in AUTHORS.md.

License

See LICENSE.md for more information on our MIT license.

Copyright !ninja