issues
search
AndreasMadsen
/
trace
Creates super long stack traces
https://trace.js.org
MIT License
194
stars
18
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Swallowing errors with Axios
#56
markwylde
closed
2 months ago
3
Error security context
#55
Somebi
opened
4 years ago
0
Control stack trace reset
#54
nknapp
closed
5 years ago
0
Error: Conflicting version of stack-chain found
#53
joniba
closed
5 years ago
4
Update test expectations to pass on node v11
#52
cspotcode
closed
5 years ago
0
[test] Ignore stack lines from outside our test code
#51
cspotcode
closed
5 years ago
3
Fix promise traces
#50
cspotcode
opened
5 years ago
1
Small bugfixes & features
#49
cspotcode
closed
5 years ago
2
Adds .editorconfig
#48
cspotcode
closed
5 years ago
1
Enables eslint:recommended linter rules
#47
cspotcode
closed
5 years ago
1
`executionScopeDepth` does not make sense if concurrent async operations
#46
cspotcode
closed
5 years ago
1
Memory leak
#45
Sprit3Dan
opened
5 years ago
4
Treating error.stack as immutable?
#44
alcuadrado
closed
5 years ago
2
Add an `install` method
#43
ehmicky
closed
6 years ago
1
Do not show timer.js and async_hooks.js internals in stack trace
#42
ehmicky
closed
5 years ago
1
Add GitHub releases
#41
ehmicky
closed
6 years ago
2
Follow promises across resolve
#40
jbunton-atlassian
opened
6 years ago
3
Conflict of stack-trace version with the one from clarify
#39
Alexsey
closed
6 years ago
1
Usage with electron
#38
7c
closed
5 years ago
1
Change engine field to be >=8 instead of ^8
#37
maritz
closed
6 years ago
5
Stack Trace makes no sense
#36
ben-page
closed
5 years ago
3
Memory leak of sorts
#35
abrenneke
opened
6 years ago
5
The dreaded "throwing after await"
#34
fasterthanlime
opened
7 years ago
19
Fixed syntax errors in readme
#33
amilajack
closed
7 years ago
1
Uid stack fix
#32
AndreasMadsen
closed
7 years ago
0
Compatibility with node ^7.0
#31
BartWaardenburg
closed
7 years ago
2
current uid is a stack
#30
AndreasMadsen
closed
7 years ago
1
I get this error when running node 4.4.5
#29
kevbook
closed
8 years ago
2
Source map support
#28
darky
closed
8 years ago
2
does it work in frontend when used with webpack/browserify
#27
sagiavinash
closed
8 years ago
1
TypeError: Cannot read property 'apply' of undefined
#26
cdaringe
closed
8 years ago
4
Make it work again with 4.4.3 LTS again
#25
FlorianLoch
closed
8 years ago
3
Recent async-hook update breaks trace on node v4
#24
timkendrick
closed
8 years ago
4
attempting to print the stack results in a TypeError
#23
cdaringe
closed
8 years ago
2
SyntaxError: Use of const in strict mode.
#22
agirorn
closed
8 years ago
1
Getting "node::AsyncWrap::AsyncWrap init hook threw" error when using 2.0.2
#21
saintedlama
closed
8 years ago
5
Failing on node 0.12
#20
Jimbly
closed
8 years ago
3
AsyncWrap init hook threw
#19
julien-f
closed
8 years ago
7
Memory leak with clearTimeout
#18
AndreasMadsen
closed
8 years ago
1
Memory usage with fs.createReadStream()
#17
julien-f
closed
8 years ago
7
setTimeout() returns undefined under Node 4 since trace 2.0
#16
julien-f
closed
8 years ago
2
Issue with Node 4
#15
julien-f
closed
8 years ago
3
Compatibility with Node 4
#14
julien-f
closed
8 years ago
4
trace & iojs, plans, compatibility?
#13
iliakan
closed
9 years ago
5
tracing core module and node 0.11.15
#12
mpal9000
closed
9 years ago
7
Wrong stack?
#11
iliakan
closed
9 years ago
3
Out of memory
#10
iliakan
closed
9 years ago
29
Doesn't really work
#9
iliakan
closed
9 years ago
48
Missing dependency 'tracing'
#8
kilokeith
closed
10 years ago
1
build failing
#7
smirea
closed
10 years ago
5
Next