verror

npmv1.10.1

richer JavaScript errors

Not recommended for new projects

No — verror should not be adopted for new projects. Last published 1772 days ago.

AAdoption: grade A, Excellent.
19.8M downloads per week and 1 known dependents.
FMaintenance: grade F, Failing.
Last published 1772 days ago.
AWeight: grade A, Excellent.
Pulls in 3 transitive packages, about 64 KB installed (at least — some of the tree is still being crawled).
ASupply chain: grade A, Excellent.
No install scripts, 14 maintainers, and a contained dependency surface.
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 verror to a project.

Direct dependencies

Runtime packages this one declares itself.

Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

64 KB

Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

MIT

Every license you inherit by installing verror, not just its own. Check this before a legal review, not after.

Compatibility

Node.js: node >=0.6.0
Module format: CommonJS only
TypeScript: No bundled types
Install scripts: None

Quick start

A usage example from the verror README.

javascriptFull README ↗

var err = new VError('missing file: "%s"', '/etc/passwd');
console.log(err.message);

verror vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

Package	Weekly downloads	Dependents	License	Last release
verrorthis page	19.8M	1	MIT	4 years ago
make-error	0	1	ISC	1 day ago
graceful-fs	0	24	ISC	1 day ago
stacktrace-parser	0	4	MIT	1 day ago
http-errors	149.4M	7	MIT	1 day ago
es-errors	0	15	MIT	1 day ago

Dependencies

Declared by verror v1.10.1. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (3)

assert-plus ^1.0.0core-util-is 1.0.2extsprintf ^1.2.0

Used by

Popular packages that depend on verror.

jsprimnpm

utilities for primitive JavaScript types

↓ 14M/wk◈ 1 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of verror.

verror dependencies dependents

Frequently installed together

extsprintfnpm

extended POSIX-style sprintf

↓ 23.5M/wk◈ 2 dependents⚖ MIT

assert-plusnpm

Extra assertions on top of node's assert module

↓ 0/wk◈ 6 dependents⚖ MIT

json-schemanpm

JSON Schema validation and specifications

↓ 0/wk◈ 2 dependents⚖ (AFL-2.1 OR BSD-3-Clause)

Release history

No releases in the last two years, typically about 57 days apart.

Recent versions of verror
Version	Published	Size	License
1.10.1latest	4 years ago	35 KB	MIT
1.10.0	9 years ago	—	MIT
1.9.0	9 years ago	—	MIT
1.8.1	10 years ago	—	MIT
1.8.0	10 years ago	—	MIT
1.7.0	10 years ago	—	MIT
1.6.1	10 years ago	—	MIT
1.6.0	11 years ago	—	MIT
1.5.1	11 years ago	—	MIT
1.5.0	11 years ago	—	MIT
1.4.0	12 years ago	—	MIT
1.3.7	12 years ago	—	MIT
1.3.6	13 years ago	—	MIT
1.3.5	13 years ago	—	MIT
1.3.4	14 years ago	—	MIT

Overview

verror is an npm package that richer JavaScript errors. It is extremely widely used, with about 19.8M downloads per week and 1 known dependents in the graph. The latest version is 1.10.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need richer JavaScript errors and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

Large, well-established user base (19.8M weekly downloads).
Clear open-source license (MIT).
Lean dependency tree (3 direct dependencies).

Cons

No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

arekinath bahamat chudley dap dbuell jclulow kellymclaughlin kusor melloc michael.hicks tchameroy todd.whiteman trentm wyatt

Keywords

custom err error errors exception exceptions

Frequently asked questions

Should I use verror?

No — verror should not be adopted for new projects. Last published 1772 days ago.

How do I install verror?

Run `npm install verror` to add verror to your npm project.

How many dependencies does verror have?

verror declares 3 direct dependencies and pulls in 3 packages in total once its runtime tree is resolved totalling about 64 KB on disk.

What license is verror released under?

verror is distributed under the MIT license.

How popular is verror?

verror has approximately 19,826,227 downloads per week and 1 known dependent packages.

Is verror still maintained?

The most recent release of verror (v1.10.1) was published 4 years ago.

Does verror run install scripts?

No. verror does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.