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

handy-debugger

v0.1.0

Published

easily debug your Nodejs app in the Chromium Devtools

Downloads

3

Readme

handy-debugger

Run your Node.js apps in an Electron window for dead-simple debugging

This works by starting an Electron instance, and then loading your code into the Electron instance.

Why not use node-inspector, debugger, or XYZ npm package?

  • less dependencies
  • handy-debugger will hot-reload code changes and rerun your script when you refresh the window (ctrl/cmd + r), unlike node-inspector
  • does not install electron-prebuilt locally, relying on a globally installed Electron binary
  • provides stdout and stderr both on the command line, and in the devtools
  • stdin in the terminal will continue to work as expected for interactive node software
  • generally works more consistently and throws less errors, which is useful in a debugging tool

Dependencies

You must have the Electron binary available on your path:

npm install -g electron-prebuilt

usage

From the command line (preferred):

handy-debugger path/to/my/script anArgument anotherArg endlessArgs ...

handy-debugger global-npm-command someArg

In your script:

if (!require('handy-debugger')()) {
  doTheScriptStuff();
}

The guard is required to prevent your script continuing to run outside of the debugger instance. The debugger will launch your script as well,

You should prevent your script from doing work if it is running outside Electron, as Electron will launch your script as well, potentially leading to two copies of your script executing in parallel.

Note: You may need to refresh the electron window after the initial load to hit your breakpoints. Refreshing the debugger will reload any code changes and rerun the script.

API

var spawn = require('handy-debugger')

Returns a function that spawns the debugger. The function will return false when your script is being run in the debugger. The function will return the Electron child process when your script is running outside of the debugger.