What is stacktrace-parser?
The stacktrace-parser npm package is a utility for parsing stack traces generated by errors in JavaScript. It can parse the stack string of an error into a more structured format, making it easier to understand and process programmatically. This can be particularly useful for error handling, logging, and debugging purposes.
What are stacktrace-parser's main functionalities?
Parse Error Stack Trace
This feature allows you to parse the stack trace of an error into a structured format. The parsed stack trace includes details such as the file name, method name, line number, and column number where the error occurred. This makes it easier to pinpoint the source of errors in your code.
const stacktraceParser = require('stacktrace-parser');
const stack = stacktraceParser.parse(new Error('Test error').stack);
console.log(stack);
Other packages similar to stacktrace-parser
error-stack-parser
Similar to stacktrace-parser, error-stack-parser provides functionality for parsing and extracting information from error stack traces. It offers a slightly different API and may have differences in the parsing logic or the structure of the parsed output, making it an alternative depending on specific needs or preferences.
stack-trace
This package offers functionality to get stack traces of the current position in code execution, in addition to parsing existing stack traces. It provides a broader set of features related to stack traces, including the ability to generate and parse them, which might make it a more versatile choice for certain applications.
StackTrace-Parser
This parser parses a stack trace from any browser or Node.js and returns an array of hashes representing a line.
Usage
try {
throw new Error('My error');
} catch(ex) {
var lines = StackTraceParser.parse(ex.stack);
}
Every line contains four properties: lineNumber
, methodName
, file
and column
(if applicable).
TODOs
- allow to run in browser (v0.2)
- parse stack traces from other sources (Ruby, etc) (v0.3)
Contribution
If you want to contrib, then do you thing, write tests, run grunt test
ensure that everything is green , commit and make the pull request. Or just write an issue, or let's talk.
Contributors
LICENSE
The MIT License (MIT)
Copyright (c) 2014-2015 Georg Tavonius
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.