error-stack-parser
npmv2.1.4TypeScriptExtract meaning from JS Errors
Not recommended for new projects
No — error-stack-parser should not be adopted for new projects. Last published 1556 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1556 days ago.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 58 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 5 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 error-stack-parser 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.
Licenses in the dependency tree
Every license you inherit by installing error-stack-parser, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the error-stack-parser README.
ErrorStackParser.parse(new Error('BOOM'));
=> [
StackFrame({functionName: 'foo', args: [], fileName: 'path/to/file.js', lineNumber: 35, columnNumber: 79, isNative: false, isEval: false}),
StackFrame({functionName: 'Bar', fileName: 'https://cdn.somewherefast.com/utils.min.js', lineNumber: 1, columnNumber: 832, isNative: false, isEval: false, isConstructor: true}),
StackFrame(... and so on ...)
]error-stack-parser 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 |
|---|---|---|---|---|
| error-stack-parserthis page | 0 | 2 | MIT | 4 years ago |
| callsites | 136.7M | 1 | MIT | 2 days ago |
| stackframe | 0 | 1 | MIT | 2 days ago |
| stacktrace-parser | 0 | 4 | MIT | 2 days ago |
| commander | 451.1M | 11 | MIT | 2 days ago |
| postcss | 249.3M | 7 | MIT | 2 days ago |
Dependencies
Declared by error-stack-parser v2.1.4. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (16)
Used by
Popular packages that depend on error-stack-parser.
Relationship graph
Dependencies (left) and dependents (right) of error-stack-parser.
Frequently installed together
TypeScript definitions for node
Prettier is an opinionated code formatter
A Long class for representing a 64-bit two's-complement integer value.
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files
Module that helps you write generated functions in Node
🛡️ Faster SQL escape and format for JavaScript (Node.js, Bun, and Deno).
sql named placeholders to unnamed compiler
AWS RDS SSL certificates bundles.
Convert character encodings in pure javascript.
The fastest javascript implementation of a double-ended queue. Used by the official Redis, MongoDB, MariaDB & MySQL libraries for Node.js and many other libraries. Maintains compatability with deque.
Lightweight debugging utility for Node.js and the browser
The ultimate javascript content-type utility.
Release history
No releases in the last two years, typically about 36 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.1.4latest | 4 years ago | 35 KB | MIT |
| 2.1.3 | 4 years ago | 35 KB | MIT |
| 2.1.2 | 4 years ago | 35 KB | MIT |
| 3.0.0 | 4 years ago | 35 KB | MIT |
| 2.1.1 | 4 years ago | 35 KB | MIT |
| 2.1.0 | 4 years ago | 35 KB | MIT |
| 2.0.7 | 4 years ago | 36 KB | MIT |
| 2.0.6 | 6 years ago | 37 KB | MIT |
| 2.0.5 | 6 years ago | 32 KB | MIT |
| 2.0.4 | 7 years ago | 51 KB | MIT |
| 2.0.3 | 7 years ago | 49 KB | MIT |
| 2.0.2 | 8 years ago | 47 KB | MIT |
| 2.0.1 | 9 years ago | — | MIT |
| 2.0.0 | 9 years ago | — | Unlicense |
| 1.3.6 | 10 years ago | — | Unlicense |
Overview
error-stack-parser is an npm package that extract meaning from JS Errors. It has 2 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 extract meaning from JS Errors and value a focused 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
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- Large dependency tree (17 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Keywords
Frequently asked questions
Should I use error-stack-parser?
No — error-stack-parser should not be adopted for new projects. Last published 1556 days ago.
How do I install error-stack-parser?
Run `npm install error-stack-parser` to add error-stack-parser to your npm project.
How many dependencies does error-stack-parser have?
error-stack-parser declares 17 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 58 KB on disk.
What license is error-stack-parser released under?
error-stack-parser is distributed under the MIT license.
How popular is error-stack-parser?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on error-stack-parser.
Is error-stack-parser still maintained?
The most recent release of error-stack-parser (v2.1.4) was published 4 years ago.
Does error-stack-parser run install scripts?
No. error-stack-parser does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.