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

noodebug

v1.0.6

Published

A simple debugging utility for logging, dumping, and Express.js response debugging.

Readme

Here is a properly structured README.md file for your noodebug NPM package:


📦 noodebug

A simple debugging utility for logging, dumping, and Express.js response debugging.
Easily debug your Node.js applications with structured logs, colored output, and Express.js support.


🚀 Installation

Install the package using npm or yarn:

npm install noodebug

or

yarn add noodebug

📖 Usage

1️⃣ Basic Debugging

Import the package in your Node.js project:

const { dd, dump } = require("noodebug");

🔹 dump(...data) - Logs data without stopping execution

dump("Hello, World!", { name: "Alice", age: 25 });

Example Output:

██████████████████████████████████████████████
🔍 DUMP at 2025-03-10T10:00:00.000Z
██████████████████████████████████████████████

👉 Param 1:
'Hello, World!'

👉 Param 2:
{ name: 'Alice', age: 25 }

🔹 dd(...data) - Logs data and stops execution

dd("Fatal Error", { error: "Something went wrong", code: 500 });

Example Output (Execution Stops After This):

██████████████████████████████████████████████
🔍 DUMP & DIE at 2025-03-10T10:00:00.000Z
██████████████████████████████████████████████

👉 Param 1:
'Fatal Error'

👉 Param 2:
{ error: 'Something went wrong', code: 500 }

🚫 Execution stopped.

2️⃣ Using in an Express.js API

dump and dd can also work with Express.js response objects.

🔹 dd(res, ...data) - Sends JSON response and stops execution

const express = require("express");
const { dd, dump } = require("noodebug");

const app = express();

app.get("/", (req, res) => {
  dd(res, { success: false, message: "An error occurred" });
});

app.listen(3000, () => console.log("Server running on port 3000"));

Example JSON Response:

{
  "status": "terminated",
  "timestamp": "2025-03-10T10:00:00.000Z",
  "data": [
    {
      "success": false,
      "message": "An error occurred"
    }
  ]
}

(Execution stops after sending the response.)


🔹 dump(res, ...data) - Sends JSON response but continues execution

app.get("/debug", (req, res) => {
  dump(res, { message: "Debugging API response" });
  console.log("This will still run.");
});

Example JSON Response:

{
  "status": "debug",
  "timestamp": "2025-03-10T10:00:00.000Z",
  "data": [
    {
      "message": "Debugging API response"
    }
  ]
}

(Execution continues after sending the response.)


⚙️ Configuration (Optional)

By default, logs print to the console. You can also enable logging to a file.

  1. Open index.js in noodebug
  2. Set LOG_TO_FILE = true
  3. Logs will be saved in debug.log
const LOG_TO_FILE = true; // Enables logging to file

📜 License

This package is licensed under the MIT License.


🤝 Contributing

  1. Fork the repository
  2. Create a new branch (feature-xyz)
  3. Commit changes and push
  4. Open a pull request

🌟 Support

If you find this package helpful, please star ⭐ the repo and share!
For issues, open a GitHub issue or contact me.


This README provides clear installation, usage examples, Express.js integration, and configuration details, making it developer-friendly! 🚀