</>PackageGraphPackageGraph

make-error

npmv1.3.6

Make your own error types!

Not recommended for new projects

No — make-error should not be adopted for new projects. Last published 2394 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 2394 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 12 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 3 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    ISC — 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 make-error to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

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

12 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the make-error README.

javascriptFull README ↗
var makeError = require("make-error");

make-error vs the alternatives

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

PackageWeekly downloadsDependentsLicenseLast release
make-errorthis page01ISC6 years ago
verror19.8M1MIT18 hours ago
make-dir02MIT18 hours ago
graceful-fs024ISC17 hours ago
non-error01MIT18 hours ago
http-errors149.4M7MIT18 hours ago

Dependencies

Declared by make-error v1.3.6. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (12)

browserify ^16.2.3eslint ^6.5.1eslint-config-prettier ^6.4.0eslint-config-standard ^14.1.0eslint-plugin-import ^2.14.0eslint-plugin-node ^10.0.0eslint-plugin-promise ^4.0.1eslint-plugin-standard ^4.0.0husky ^3.0.9jest ^24prettier ^1.14.3uglify-js ^3.3.2

Used by

Popular packages that depend on make-error.

ts-nodenpm

TypeScript execution environment and REPL for node.js, with source map support

↓ 42.2M/wk◈ 38 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of make-error.

ts-nodemake-error
make-error dependencies dependents

Frequently installed together

@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS
@swc/wasmnpm

wasm module for swc

↓ 0/wk◈ 1 dependents⚖ Apache-2.0TS
acornnpm

ECMAScript parser

↓ 221.9M/wk◈ 19 dependents⚖ MITTS
reactnpm

React is a JavaScript library for building user interfaces.

↓ 152.8M/wk◈ 82 dependents⚖ MIT
lodashnpm

Lodash modular utilities.

↓ 147.8M/wk◈ 20 dependents⚖ MIT
diffnpm

A JavaScript text diff implementation.

↓ 124.1M/wk◈ 4 dependents⚖ BSD-3-ClauseTS
axiosnpm

Promise based HTTP client for the browser and node.js

↓ 106.5M/wk◈ 4 dependents⚖ MITTS
acorn-walknpm

ECMAScript (ESTree) AST walker

↓ 70.4M/wk◈ 3 dependents⚖ MITTS
ynnpm

Parse yes/no like values

↓ 30.3M/wk◈ 1 dependents⚖ MITTS
@tsconfig/node14npm

A base TSConfig for working with Node 14.

↓ 0/wk◈ 2 dependents⚖ MIT
@tsconfig/node16npm

A base TSConfig for working with Node 16.

↓ 0/wk◈ 2 dependents⚖ MIT
argnpm

Unopinionated, no-frills CLI argument parser

↓ 0/wk◈ 3 dependents⚖ MITTS

Release history

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

Recent versions of make-error
VersionPublishedSizeLicense
1.3.6latest6 years ago12 KBISC
1.3.58 years ago11 KBISC
1.3.48 years ago11 KBISC
1.3.38 years ago—ISC
1.3.28 years ago—ISC
1.3.18 years ago—ISC
1.3.09 years ago—ISC
1.2.39 years ago—ISC
1.2.29 years ago—ISC
1.2.110 years ago—ISC
1.2.010 years ago—ISC
1.1.110 years ago—ISC
1.1.010 years ago—ISC
1.0.411 years ago—ISC
1.0.311 years ago—ISC

Overview

make-error is an npm package that make your own error types!. It has 1 known dependents in the graph. The latest version is 1.3.6, released under the ISC license.

Who should use it

Teams working in the npm ecosystem who need make your own error types! and value a focused 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

  • Clear open-source license (ISC).

Cons

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

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

Maintainers

julien-fmarsaudpdonias

Keywords

createcustomderiveerrorerrorsextendextendingextensionfactoryinheritmakesubclass

Frequently asked questions

Should I use make-error?

No — make-error should not be adopted for new projects. Last published 2394 days ago.

How do I install make-error?

Run `npm install make-error` to add make-error to your npm project.

What license is make-error released under?

make-error is distributed under the ISC license.

How popular is make-error?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on make-error.

Is make-error still maintained?

The most recent release of make-error (v1.3.6) was published 6 years ago.

Does make-error run install scripts?

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