Gathering detailed insights and metrics for stack-trace
Gathering detailed insights and metrics for stack-trace
Gathering detailed insights and metrics for stack-trace
Gathering detailed insights and metrics for stack-trace
Get v8 stack traces as an array of CallSite objects.
npm install stack-trace
99.9
Supply Chain
99.5
Quality
81.9
Maintenance
100
Vulnerability
100
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
453 Stars
74 Commits
41 Forks
7 Watching
11 Branches
14 Contributors
Updated on 20 Nov 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-2.1%
2,585,021
Compared to previous day
Last week
3.1%
14,020,951
Compared to previous week
Last month
12.1%
57,327,631
Compared to previous month
Last year
5.3%
604,857,633
Compared to previous year
4
Get v8 stack traces as an array of CallSite objects.
1npm install stack-trace
The stack-trace module makes it easy for you to capture the current stack:
1import { get } from 'stack-trace'; 2const trace = get(); 3 4expect(trace[0].getFileName()).toBe(__filename);
However, sometimes you have already popped the stack you are interested in,
and all you have left is an Error
object. This module can help:
1import { parse } from 'stack-trace'; 2const err = new Error('something went wrong'); 3const trace = parse(err); 4 5expect(trace[0].getFileName()).toBe(__filename);
Please note that parsing the Error#stack
property is not perfect, only
certain properties can be retrieved with it as noted in the API docs below.
stack-trace works great with long-stack-traces, when parsing an err.stack
that has crossed the event loop boundary, a CallSite
object returning
'----------------------------------------'
for getFileName()
is created.
All other methods of the event loop boundary call site return null
.
Returns an array of CallSite
objects, where element 0
is the current call
site.
When passing a function on the current stack as the belowFn
parameter, the
returned array will only include CallSite
objects below this function.
Parses the err.stack
property of an Error
object into an array compatible
with those returned by stackTrace.get()
. However, only the following methods
are implemented on the returned CallSite
objects.
Note: Except getFunctionName()
, all of the above methods return exactly the
same values as you would get from stackTrace.get()
. getFunctionName()
is sometimes a little different, but still useful.
The official v8 CallSite object API can be found [here][https://github.com/v8/v8/wiki/Stack-Trace-API#customizing-stack-traces]. A quick excerpt:
A CallSite object defines the following methods:
- getThis: returns the value of this
- getTypeName: returns the type of this as a string. This is the name of the function stored in the constructor field of this, if available, otherwise the object's [[Class]] internal property.
- getFunction: returns the current function
- getFunctionName: returns the name of the current function, typically its name property. If a name property is not available an attempt will be made to try to infer a name from the function's context.
- getMethodName: returns the name of the property of this or one of its prototypes that holds the current function
- getFileName: if this function was defined in a script returns the name of the script
- getLineNumber: if this function was defined in a script returns the current line number
- getColumnNumber: if this function was defined in a script returns the current column number
- getEvalOrigin: if this function was created using a call to eval returns a CallSite object representing the location where eval was called
- isToplevel: is this a toplevel invocation, that is, is this the global object?
- isEval: does this call take place in code defined by a call to eval?
- isNative: is this call in native V8 code?
- isConstructor: is this a constructor call?
stack-trace is licensed under the MIT license.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 11/17 approved changesets -- score normalized to 6
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
19 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
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