source: frontend/node_modules/stack-utils/readme.md

Last change on this file was 9af201e, checked in by MBK <marija.karapandzova@…>, 12 days ago

Fix frontend appearance

  • Property mode set to 100644
File size: 4.5 KB
Line 
1# stack-utils
2
3> Captures and cleans stack traces.
4
5[![Linux Build](https://travis-ci.org/tapjs/stack-utils.svg?branch=master)](https://travis-ci.org/tapjs/stack-utils) [![Build status](https://ci.appveyor.com/api/projects/status/fb9i157knoixe3iq/branch/master?svg=true)](https://ci.appveyor.com/project/jamestalmage/stack-utils-oiw96/branch/master) [![Coverage](https://coveralls.io/repos/tapjs/stack-utils/badge.svg?branch=master&service=github)](https://coveralls.io/github/tapjs/stack-utils?branch=master)
6
7
8Extracted from `lib/stack.js` in the [`node-tap` project](https://github.com/tapjs/node-tap)
9
10## Install
11
12```
13$ npm install --save stack-utils
14```
15
16
17## Usage
18
19```js
20const StackUtils = require('stack-utils');
21const stack = new StackUtils({cwd: process.cwd(), internals: StackUtils.nodeInternals()});
22
23console.log(stack.clean(new Error().stack));
24// outputs a beautified stack trace
25```
26
27
28## API
29
30
31### new StackUtils([options])
32
33Creates a new `stackUtils` instance.
34
35#### options
36
37##### internals
38
39Type: `array` of `RegularExpression`s
40
41A set of regular expressions that match internal stack stack trace lines which should be culled from the stack trace.
42The default is `StackUtils.nodeInternals()`, this can be disabled by setting `[]` or appended using
43`StackUtils.nodeInternals().concat(additionalRegExp)`. See also `ignoredPackages`.
44
45##### ignoredPackages
46
47Type: `array` of `string`s
48
49An array of npm modules to be culled from the stack trace. This list will mapped to regular
50expressions and merged with the `internals`.
51
52Default `''`.
53
54##### cwd
55
56Type: `string`
57
58The path to the current working directory. File names in the stack trace will be shown relative to this directory.
59
60##### wrapCallSite
61
62Type: `function(CallSite)`
63
64A mapping function for manipulating CallSites before processing. The first argument is a CallSite instance, and the function should return a modified CallSite. This is useful for providing source map support.
65
66
67### StackUtils.nodeInternals()
68
69Returns an array of regular expressions that be used to cull lines from the stack trace that reference common Node.js internal files.
70
71
72### stackUtils.clean(stack, indent = 0)
73
74Cleans up a stack trace by deleting any lines that match the `internals` passed to the constructor, and shortening file names relative to `cwd`.
75
76Returns a `string` with the cleaned up stack (always terminated with a `\n` newline character).
77Spaces at the start of each line are trimmed, indentation can be added by setting `indent` to the desired number of spaces.
78
79#### stack
80
81*Required*
82Type: `string` or an `array` of `string`s
83
84
85### stackUtils.capture([limit], [startStackFunction])
86
87Captures the current stack trace, returning an array of `CallSite`s. There are good overviews of the available CallSite methods [here](https://github.com/v8/v8/wiki/Stack%20Trace%20API#customizing-stack-traces), and [here](https://github.com/sindresorhus/callsites#api).
88
89#### limit
90
91Type: `number`
92Default: `Infinity`
93
94Limits the number of lines returned by dropping all lines in excess of the limit. This removes lines from the stack trace.
95
96#### startStackFunction
97
98Type: `function`
99
100The function where the stack trace should start. The first line of the stack trace will be the function that called `startStackFunction`. This removes lines from the end of the stack trace.
101
102
103### stackUtils.captureString([limit], [startStackFunction])
104
105Captures the current stack trace, cleans it using `stackUtils.clean(stack)`, and returns a string with the cleaned stack trace. It takes the same arguments as `stackUtils.capture`.
106
107
108### stackUtils.at([startStackFunction])
109
110Captures the first line of the stack trace (or the first line after `startStackFunction` if supplied), and returns a `CallSite` like object that is serialization friendly (properties are actual values instead of getter functions).
111
112The available properties are:
113
114 - `line`: `number`
115 - `column`: `number`
116 - `file`: `string`
117 - `constructor`: `boolean`
118 - `evalOrigin`: `string`
119 - `native`: `boolean`
120 - `type`: `string`
121 - `function`: `string`
122 - `method`: `string`
123
124### stackUtils.parseLine(line)
125
126Parses a `string` (which should be a single line from a stack trace), and generates an object with the following properties:
127
128 - `line`: `number`
129 - `column`: `number`
130 - `file`: `string`
131 - `constructor`: `boolean`
132 - `evalOrigin`: `string`
133 - `evalLine`: `number`
134 - `evalColumn`: `number`
135 - `evalFile`: `string`
136 - `native`: `boolean`
137 - `function`: `string`
138 - `method`: `string`
139
140
141## License
142
143MIT © [Isaac Z. Schlueter](http://github.com/isaacs), [James Talmage](http://github.com/jamestalmage)
Note: See TracBrowser for help on using the repository browser.