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

devbug

v0.1.3

Published

Debug your app with a much better console.log() alternative

Downloads

692

Readme

Devbug

Debug your node app with a much better console.log() alternative. Devbug will do a better job formatting the variables you want to output and allow you to choose colors so you don't get confused when debugging. Additionally, devbug provides you with a master on-off switch so you can disable all your debug outputs for production.

Installation

npm install --save devbug

Usage

First create a property called debugmode in your local package.json file:

...
"dependencies": {
    "mocha": "^3.5.3",
    "nyc": "^11.2.1"
  },
"debugmode": true

Then simply pull out the methods you need and use them:

const {dbg,colors} = require('devbug');

dbg(<summary>,<variable to display>,<color>);

Examples

Debugging

Reminder: In your package.json file make sure you add a property called 'debugmode' and set it to true for this to work:

const {dbg,colors} = require('devbug');

const plotPoint = {x:3, y:10}
dbg("Temperate weather", plotPoint, colors.WHITE);

plotPoint.x = 5
dbg("Warm weather", plotPoint, colors.YELLOW);

plotPoint.x = 10
dbg("Hot weather", plotPoint, colors.RED);

Messaging

Unlike dbg (above), msg works even when 'debugmode' is set to false:

const {msg,colors} = require('devbug');

try {
    return processObject(obj)
  } catch (error) {
    msg('Error', 'There was a problem processing the object', colors.RED);
  }

Support

If you experience any bugs or issues please post a comment here: https://github.com/Firebrand/devbug/issues Typically it will get responded to and resolved within 24hrs. Make sure to include the error message as well as the css you are inputting into it.

License

ISC