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

debugit

v1.0.1

Published

A no frills console debugger for Node.

Downloads

4

Readme

debugIt

Build Status

A no frills console debugger for Node.

Use this module when you want to selectively choose when you want to enable logging to your console. This is a handy little tool for debugging works in progress, or to only show logs when running tests.

Heavily inspired by visionmedia/debug. But instead of enabling debugging in your terminal environment, you enable debugIt in your code.

  • Works across exports within your project
  • Semi-Unique colors for different debug namespaces
  • An easy to use, simple interface

Note: This module is only for command line debugging.

Installation

npm install --save debugit

Basic Usage

Set Up Namespaces

You can set up your debug logs using the debugit.add(namespaceName) method. They won't get printed to the console until debugIt is enabled globally.

var debugMain = require('debugit').add('debugit:main')
var debugSecondary = require('debugit').add('debugit:secondary')

Write to Your Namespaces

Now you can write to these namespaces. Each namespace will be presented in a color based on its name, so you can tell them apart.

var x = 5
var y = 'something else'

debugMain('what is the value of x?', x, 'is the value of x.')
debugSecondary('what is the value of y?', y, 'is the value of y.')

Enable It

Finally in your main.js or test file, at the very very top, just enable debugIt when you want to enable the logs.

var debugIt = require('debugit').enable()

Note: Currently there's no way to selectively choose which namespaces to turn on.

License

The MIT License (MIT)

Copyright (c) 2014 Arjun Mehta