debug-js/debug

A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 52 minutes ago
Added to GitGenius on September 5th, 2026
Created on November 29th, 2011
Open Issues & Pull Requests: 96 (+0)
GitHub issues: Enabled
Number of forks: 989
Total Stargazers: 11,453 (+0)
Total Subscribers: 134 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.0 hours
Mean response time: 97.1 days
90th percentile: 244.6 days
Tracked items: 53

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 3% of issues opened in the past year have been closed. Three people close 84% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 20
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,085 days
Stale 30+ days: 18
Stale 90+ days: 18

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (5)
  • question (3)
  • change-minor (1)
  • change-patch (1)
  • feature (1)
  • help-wanted (1)
  • needs-documentation (1)
  • pr-welcome (1)

Most active issues this week

Detailed Description

debug is a tiny JavaScript debugging utility that works in Node.js and web browsers.

The tool solves the problem of selectively enabling and disabling debug output across different parts of an application without modifying code. It works by exposing a function that takes a module name and returns a decorated console.error function. Developers toggle debug output using the DEBUG environment variable with space or comma-delimited namespace names, supporting wildcards and exclusion patterns. Each debug instance receives a generated color based on its namespace to aid visual parsing of output. The tool also displays millisecond differences between consecutive debug calls, showing elapsed time during development.

The tool suits developers who want lightweight, zero-configuration debugging without adding logging frameworks to their codebase. It works equally well in Node.js and browsers, making it useful for full-stack JavaScript projects. The namespace convention of using library names with colon-separated features allows multiple debuggers to coexist without naming conflicts. Developers should install the supports-color module alongside debug in Node.js to access the full color palette; without it, only basic colors are available. Browser support includes WebKit inspectors, Firefox, and Firebug, all of which understand the %c formatting option for styled console output.

The project maintains active engagement with its community through public funding mechanisms. Development shows consistent responsiveness to issues and pull requests, with maintainers actively reviewing and merging contributions. The codebase receives regular updates addressing edge cases and compatibility concerns across different environments. Documentation is thorough and includes platform-specific guidance for Windows command prompt and PowerShell users, reflecting attention to developer experience across operating systems.