TritonDataCenter/node-verror
Rich JavaScript errors observed · 2026-08-28
Health v2 · maintenance only
60/100
- Activity 62
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 5251
- days_rel: n/a
- days_push: 232
- n_releases_24m: 0
Adoption not part of the score
1191 stars · 57 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
node-verror is a JavaScript library providing rich error classes (VError, WError, SError, MultiError) for Node.js. It supports printf-style messages, error cause chains, extra informational properties, and custom subclasses.
Use cases
- chain errors with context across call stack layers
- wrap internal errors without exposing messages to API clients
- create error subclasses with printf-style messages
- aggregate multiple errors from parallel operations
- attach extra metadata to errors for debugging
When to choose
- you follow Joyent-style Node.js error handling best practices
- you need structured error cause chains with rich messages
- you want to hide internal error details from API consumers while preserving them for logs
When to avoid
- you only need simple built-in Error objects
- your project uses modern alternatives like AggregateError or custom error classes
- you are not working in a Node.js/JavaScript codebase
Facets
library · maturity stable
error-handling backend developer-tools errors error-chaining javascript nodejs
1 source
- readme: https://github.com/TritonDataCenter/node-verror · fetched 2026-08-28 · c556fbd6b61c
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| TritonDataCenter/node-verror | main | 60 |
For agents
markdown · JSON · MCP: product_card(name="TritonDataCenter/node-verror")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem