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

thebugger

v1.0.0

Published

The easiest way to debug your nodejs process.

Downloads

9

Readme

thebugger · GitHub license npm version

Note: works only on node version 8 or bigger

The problem

Debugging currently requires proving the main node process flags like --inspect and/or --inspect-brk.

It works great, but most of the times I don't have full control over the process flags because I'm executing the process through a wrapper, generally jest, mocha or gulp and so many others.

This module opens the inspector and stops the process when thebugger() is called, allowing folks to debug any nodejs process without having to pass any flags.

Usage

Install thebugger as a dev dependency:

npm i --save-dev thebugger
# or
yarn add --dev thebugger

Add thebugger() to the line of code you want to start debugging, which is where you'd add a debugger; statement.

require('thebugger')();

Wait untill your nodejs process prints:

Debugger listening on ws://127.0.0.1:9222/038a3e89-b497-4558-9709-6a3da5ec3803
For help see https://nodejs.org/en/docs/inspector

Now you can open any Chrome DevTools and click on the green nodejs icon. Further instructions at: https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27

You also can use any DevTools frontend of your preference.