stacktrace-parser
npmv0.1.11TypeScriptParses every stack trace into a nicely formatted array of hashes.
Adopt with care
stacktrace-parser is usable, with caveats. Last published 568 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- CMaintenance: grade C, Fair — worth a look.
Last published 568 days ago.
- AWeight: grade A, Excellent.
Pulls in 2 transitive packages, about 575 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- 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 stacktrace-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 stacktrace-parser, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=6
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
stacktrace-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 |
|---|---|---|---|---|
| stacktrace-parserthis page | 0 | 4 | MIT | 1 year ago |
| verror | 19.8M | 1 | MIT | 1 day ago |
| error-stack-parser | 0 | 2 | MIT | 1 day ago |
| commander | 451.1M | 11 | MIT | 1 day ago |
| postcss | 249.3M | 7 | MIT | 1 day ago |
| yargs-parser | 178.8M | 2 | ISC | 1 day ago |
Dependencies
Declared by stacktrace-parser v0.1.11. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (16)
Used by
Popular packages that depend on stacktrace-parser.
A framework for building native apps using React
The Expo CLI
Error overlay for universal Expo apps.
Tools for making advanced Metro bundler features work
Relationship graph
Dependencies (left) and dependents (right) of stacktrace-parser.
Frequently installed together
The Expo SDK
Error overlay for universal Expo apps.
A framework for building native apps using React
Expo Router is a file-based router for React Native and web applications.
Stringify any JavaScript value.
React package for working with the DOM.
React is a JavaScript library for building user interfaces.
A Promise-based interface into processes created by child_process.spawn
The semantic version parser used by npm.
the most correct and second fastest glob implementation in JavaScript
A low level parser for ANSI sequences.
TypeScript definitions for react
Release history
1 release in the last two years, typically about 136 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 0.1.11latest | 1 year ago | 12 KB | MIT |
| 0.1.10 | 6 years ago | 12 KB | MIT |
| 0.1.9 | 6 years ago | 12 KB | MIT |
| 0.1.8 | 6 years ago | 16 KB | MIT |
| 0.1.7 | 7 years ago | 16 KB | MIT |
| 0.1.6 | 7 years ago | 16 KB | MIT |
| 0.1.5 | 7 years ago | 15 KB | MIT |
| 0.1.4 | 10 years ago | — | MIT |
| 0.1.3 | 11 years ago | — | MIT |
| 0.1.2 | 11 years ago | — | MIT |
| 0.1.1 | 12 years ago | — | MIT |
Overview
stacktrace-parser is an npm package that parses every stack trace into a nicely formatted array of hashes. It has 4 known dependents in the graph. The latest version is 0.1.11, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need parses every stack trace into a nicely formatted array of hashes 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.
Maintainers
Keywords
Frequently asked questions
Should I use stacktrace-parser?
stacktrace-parser is usable, with caveats. Last published 568 days ago.
How do I install stacktrace-parser?
Run `npm install stacktrace-parser` to add stacktrace-parser to your npm project.
How many dependencies does stacktrace-parser have?
stacktrace-parser declares 17 direct dependencies and pulls in 2 packages in total once its runtime tree is resolved totalling about 575 KB on disk.
What license is stacktrace-parser released under?
stacktrace-parser is distributed under the MIT license. Its dependency tree also includes: (MIT OR CC0-1.0), MIT.
How popular is stacktrace-parser?
npm does not publish download counts. Within PackageGraph's crawl, 4 known packages depend on stacktrace-parser.
Is stacktrace-parser still maintained?
The most recent release of stacktrace-parser (v0.1.11) was published 1 year ago.
Does stacktrace-parser run install scripts?
No. stacktrace-parser does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.