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 🙏

© 2026 – Pkg Stats / Ryan Hefner

ndebug

v0.1.4

Published

Easily launch interactive debugging sessions for your Node scripts.

Readme

ndebug

Using ndebug you can easily launch the Google Chrome developer tools to interactively debug your Node.js scripts while they run, providing a very pleasant and extremely producitive debugging workflow.

Under the hood, ndebug leverages the excellent node-inspector which handles all the complexity of connecting the Chrome developer tools to your running Node process. ndebug simply automates the otherwise combersome multi-step process normally required when using node-inspector by itself.

Prerequisites

  • Currently runs only on Mac
  • Node.js must be installed
  • Google Chrome must be installed at the default location /Applications/Google Chrome.app

Quick Start

Learn how to install and use ndebug in less than 2 minutes by watching this video. Or, continue reading...

Installation

Install ndebug globally using the following command...

$ sudo npm install -g ndebug

That's it!

Usage

To debug a Node.js script you're working on use the following command...

$ ndebug myscript.js

This will start your script, launch the Google Chrome developer tools, and pause your script's execution on the first line. At that point, you can add breakpoints and then resume execution of your code.

To pass arguments to your script simply append them after the command...

$ ndebug myscript.js apple banana

If, after your script has completed execution, you are not returned to a command prompt simply type Control-C to terminate the ndebug command.

To Note

This tool currently uses port 8543 for communication between Chrome and node-inspector. Customization of this port number may be provided in a future release.

Example

A simple example Node script has been provided for you to practice with. You'll find that example and instructions on how to use it here:

Simple Example