npmpackage.info

Gathering detailed insights and metrics for nested-error-stacks

Other packages similar to nested-error-stacks

@types/nested-error-stacks

2.1.2

TypeScript definitions for nested-error-stacks

@selfage/nested_error

1.0.7

Builds nested errors while preserving stacks.

Gathering detailed insights and metrics for nested-error-stacks

nested-error-stacks - 2.1.1 | npmpackage.info

nested-error-stacks

A node.js module for creating Error objects with nested Errors in stacktraces

2.1.1

MIT

JavaScript

427.00 B

977,843,016 3.6

Installations

npm install nested-error-stacks

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

14.18.2

NPM Version

6.14.15 Score

99.9

Supply Chain

Quality

75.9

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

20

Closed

3

Merged

17

Issues

Open

2

Total

6

Closed

4

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

mdlavin

Download Statistics

Total Downloads

977,843,016

Last Day

245,596

Last Week

3,484,029

Last Month

14,452,547

Last Year

149,475,136

GitHub Statistics

MIT License

94 Stars

71 Commits

13 Forks

2 Watchers

1 Branches

6 Contributors

Updated on Jan 31, 2024

Bundle Size

717.00 B

Minified

427.00 B

Minified + Gzipped

Bundlephobia

Maintainers

View All 6 Contributors

Package Meta Information

Latest Version

2.1.1

Package Id

nested-error-stacks@2.1.1

Unpacked Size

5.27 kB

Size

2.49 kB

File Count

NPM Version

6.14.15

Node Version

14.18.2

Total Downloads

Cumulative downloads

Total Downloads

977,843,016

Last Day

22%

245,596

Compared to previous day

Last Week

-1.1%

3,484,029

Compared to previous week

Last Month

0.4%

14,452,547

Compared to previous month

Last Year

-22%

149,475,136

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

chai eslint mocha uuid

Nested stacktraces for Node.js!

With this module, you can wrap a caught exception with extra context for better debugging. For example, a network error's stack would normally look like this:

Error: connect ECONNREFUSED
    at errnoException (net.js:904:11)
    at Object.afterConnect [as oncomplete] (net.js:895:19)

Using this module, you can wrap the Error with more context to get a stack that looks like this:

NestedError: Failed to communicate with localhost:8080
    at Socket.<anonymous> (/Users/mattlavin/Projects/nested-stacks/demo.js:6:18)
    at Socket.EventEmitter.emit (events.js:95:17)
    at net.js:440:14
    at process._tickCallback (node.js:415:13)
Caused By: Error: connect ECONNREFUSED
    at errnoException (net.js:904:11)
    at Object.afterConnect [as oncomplete] (net.js:895:19)

How to wrap errors

Here is an example program that uses this module to add more context to errors:

1var NestedError = require('nested-error-stacks');
2var net = require('net');
3    
4var client = net.connect({port: 8080});
5client.on('error', function (err) {
6    var newErr = new NestedError("Failed to communicate with localhost:8080", err);
7    console.log(newErr.stack);
8});

How to inherit

It is recommended to use explicit names for Error classes. You can do it like this:

1var util = require('util');
2var NestedError = require('nested-error-stacks');
3
4function MyError(message, nested) {
5    NestedError.call(this, message, nested);
6}
7
8util.inherits(MyError, NestedError);
9MyError.prototype.name = 'MyError';

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

2

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.6

/10

Last Scanned on 2025-04-28

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More