obug
npmv2.1.4TypeScriptA lightweight JavaScript debugging utility, forked from debug, featuring TypeScript and ESM support.
Safe to adopt
Yes — obug scores well across adoption, maintenance, weight, supply chain, and licensing. 61.1M downloads per week and 8 known dependents. Last published 55 days ago. 15 releases in the last 2 years.
- AAdoption: grade A, Excellent.
61.1M downloads per week and 8 known dependents.
- AMaintenance: grade A, Excellent.
Last published 55 days ago. 15 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 27 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding obug to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=12.20.0
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the obug README.
import { createDebug, disable, enable, enabled, namespaces } from 'obug'
// Get the currently enabled namespaces
console.log(namespaces())
const debug = createDebug('my-namespace', {
// All options are optional
useColors: true, // false, true, undefined for auto-detect
color: 2, // custom color
// custom formatArgs
formatArgs(args) {},
formatters: {},
// Node.js onlyDependencies
Declared by obug v2.1.4. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (16)
Used by
Popular packages that depend on obug.
Native-ESM powered web dev build tool
Next generation testing framework powered by Vite
Source maps support for istanbul
Istanbul coverage provider for Vitest
Vite DevTools
Framework for building one portable devtool integration that runs in any viewer.
The Babel Traverse module maintains the overall tree state, and is responsible for replacing, removing, and adding nodes
V8 coverage provider for Vitest
Relationship graph
Dependencies (left) and dependents (right) of obug.
Frequently installed together
Simple yet powerful framework for building command-line apps.
Universal filesystem path utils
Native-ESM powered web dev build tool
Minimal H(TTP) framework built for high performance and portability.
Structured diagnostic code library
DevTools for Rolldown
DevTools for Vite (work in progress)
DevTools for Vitest
Missing ECMAScript module utils for Node.js
Message based Two-way remote procedure call
Model Context Protocol implementation for TypeScript - Client package
A fast and minimal alternative to globby and fast-glob
Release history
15 releases in the last two years, typically about 1 day apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.1.4latest | 1 month ago | 27 KB | MIT |
| 2.1.3 | 2 months ago | 27 KB | MIT |
| 2.1.2 | 3 months ago | 26 KB | MIT |
| 2.1.1 | 9 months ago | 21 KB | MIT |
| 2.1.0 | 9 months ago | 21 KB | MIT |
| 1.0.2 | 9 months ago | 21 KB | MIT |
| 2.0.0 | 9 months ago | 21 KB | MIT |
| 2.0.0-beta.1 | 10 months ago | 20 KB | MIT |
| 1.0.0 | 10 months ago | 22 KB | MIT |
| 0.1.3 | 10 months ago | 20 KB | MIT |
| 0.1.2 | 10 months ago | 20 KB | MIT |
| 0.1.1 | 10 months ago | 21 KB | MIT |
| 0.1.0 | 10 months ago | 21 KB | MIT |
| 0.0.1 | 10 months ago | 17 KB | MIT |
| 0.0.0 | 10 months ago | 42 KB | MIT |
Overview
obug is an npm package that a lightweight JavaScript debugging utility, forked from debug, featuring TypeScript and ESM support. It is extremely widely used, with about 61.1M downloads per week and 8 known dependents in the graph. The latest version is 2.1.4, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need a lightweight JavaScript debugging utility, forked from debug, featuring TypeScript and ESM support and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (61.1M weekly downloads).
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- Large dependency tree (16 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use obug?
Yes — obug scores well across adoption, maintenance, weight, supply chain, and licensing. 61.1M downloads per week and 8 known dependents. Last published 55 days ago. 15 releases in the last 2 years.
How do I install obug?
Run `npm install obug` to add obug to your npm project.
What license is obug released under?
obug is distributed under the MIT license.
How popular is obug?
obug has approximately 61,089,615 downloads per week and 8 known dependent packages.
Is obug still maintained?
The most recent release of obug (v2.1.4) was published 1 month ago.
Does obug run install scripts?
No. obug does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.