issues
search
tlrobinson
/
long-stack-traces
Long stacktraces for V8 implemented in user-land JavaScript. [UNMAINTAINED] Use https://github.com/mattinsler/longjohn instead
277
stars
15
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Added sytnax highlighting to readme
#23
amilajack
opened
7 years ago
0
window.SVGElementInstance is undefined
#22
hulvei3
opened
9 years ago
0
Type error in long-stack-traces.js:7
#21
alinex
opened
9 years ago
2
Update long-stack-traces.js
#20
fabiancook
closed
7 years ago
0
Base code sample not working
#19
basarat
opened
10 years ago
1
doc setImmediate
#18
basarat
opened
10 years ago
0
Add setImmediate
#17
19h
closed
10 years ago
0
Is it hard/impossible to support Firefox/IE/etc?
#16
fresheneesz
opened
10 years ago
0
It provokes memory degradation
#15
christian-ciceri
opened
11 years ago
0
Make lst even more useful
#14
herzi
closed
10 years ago
1
Presence of long-stack-traces causes faulty emission of 'error' event on amqp module's Connection object
#13
weyus
opened
11 years ago
0
Throwing error when it shouldn't
#12
thanpolas
opened
11 years ago
0
Create gh-pages branch for demo
#11
ProLoser
opened
11 years ago
0
Is there an issue with Uncaught Type error
#10
digitalrinaldo
opened
12 years ago
2
Not working on http.ServerResponse closing since Node 0.6.7
#9
rstuven
opened
12 years ago
2
newbie help?
#8
mark-hahn
opened
12 years ago
1
Add option to limit stacktrace
#7
akidee
opened
13 years ago
1
events.removeListener and events.once will not work
#6
barshow
opened
13 years ago
1
Closures and some other objects seem to be leaking
#5
twills
opened
13 years ago
5
Cant find module
#4
garrensmith
closed
13 years ago
0
Add `process.nextTick()`
#3
TooTallNate
closed
13 years ago
4
add main property to support newer versions of npm
#2
polotek
closed
13 years ago
1
infinite error loop
#1
pagameba
opened
13 years ago
3