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

delay-debug

v0.0.3

Published

Debug a node projecess with node inspector, after it has started

Readme

Delay Debug

It starts node-inspector for you, and it does so until your app is running. It uses node-inspector as a dependency to inspect your app

Why?

  • Node inspector is a bit slow to start, and sometimes it is to complicated to be thinking of how to activate it when using tools like nodemon.
  • This provides a default configuration for nodeinspector with preload disabled for faster start
  • Not having to wait for node inspector in order to start your app allows you to restart the app with frequency (like nodemon reloading after a change), yet you will still be able to add breakpoints as needed if things start acting funky on your app

Installation

npm install delay-debug

Using

On your main app file (index.js)

// Your code. E.g. Like starting an http server or a service
require('http')
  .createServer(function(req, res){
    console.info('Request received: ' + req.url);
    res.end('It Works!! Path Hit: ' + req.url);
  })
  .listen(8080, function(){ console.log("Server listening on: http://localhost:%s", 8080); })
;


// Start the inspector until now
var inspector = require('delay-debug');
inspector();

From the command line start your app, make sure to include --delaydebug flag

node index.js --delaydebug

Follow the instructions on the output. Sometimes you might need to use the pause button on the debugger and then continue in order to allow the server process to continue

Configuration

You can pass a different configurations for nodeinspector by providing an object

var inspector = require('delay-debug');
inspector({
  delaydebug: {} // Normally what would go in a .node-inspectorrc
});

Pairs well with conf-stack project

var
  inspector  = require('delay-debug');
  ,confStack = require('conf-stack')
  ,config    = confStack()
;
inpector(config);
``