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

remug

v0.1.1

Published

Node.js REMmote DebUGger - Debug your Node.js applications from anywhere in the world

Readme

remug

Node.js Remote Debugger - A drop-in replacement for node that enables remote debugging via a Pinggy tunnel.

The Problem

When running Node.js applications inside Docker containers, attaching a local debugger is challenging because:

  • The container's network is isolated
  • Port 9229 (debugger port) isn't exposed
  • Even if exposed, connecting from your local machine to a remote container requires additional setup

The Solution

remug solves this by:

  1. Opening a Pinggy TCP tunnel to the debugger port (9229)
  2. Running your Node.js process with --inspect-brk (pauses at startup waiting for debugger)
  3. Printing connection instructions for your local machine
  4. Cleaning up when the process exits

Usage

Basic Usage

Prefix node with npx remug in your command:

# Before
node index.js

# After
npx remug node index.js

In Docker

Update your Dockerfile or docker-compose.yml:

# Before
CMD ["node", "index.js"]

# After
CMD ["npx", "remug", "node", "index.js"]

Or with docker-compose:

services:
  app:
    build: .
    command: npx remug node index.js

With Arguments

All arguments are passed through to Node.js:

npx remug node --experimental-modules app.mjs
npx remug node -e "console.log('hello')"
npx remug node --max-old-space-size=4096 server.js

Output Example

When you run remug, you'll see output like:

╔════════════════════════════════════════════════════════════════╗
║                   remug, the REMote DebUGger                   ║
╚════════════════════════════════════════════════════════════════╝

[remug] Starting Pinggy tunnel to localhost:9229...
[remug] Tunnel established!

✓ Remote debugger tunnel established!

═══════════════════════════════════════════════════════════════
  CONNECT FROM YOUR LOCAL MACHINE
═══════════════════════════════════════════════════════════════

  VS Code

  Add this to your launch.json:

  {
    "type": "node",
    "request": "attach",
    "name": "Attach to Remote",
    "address": "xxx.a.pinggy.link",
    "port": xxxxx,
  }

═══════════════════════════════════════════════════════════════

The Node.js process is paused waiting for debugger to attach...
Press Ctrl+C to stop the debugger and exit.

Connecting Your Debugger

VS Code

  1. Create or update .vscode/launch.json:
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "attach",
      "name": "Attach to Remote",
      "address": "xxx.a.pinggy.link",
      "port": xxxxx,
    }
  ]
}
  1. Run the SSH tunnel command from the output
  2. Press F5 or click "Run and Debug" → "Attach to Remote"

Requirements

  • Node.js 18+
  • Internet connection (for Pinggy tunnel)