Issues
- 1
- 4
Incorrectly cleans `file://` paths
#60 opened by jaydenseric - 1
Avoid property override hazard
#70 opened by FUDCo - 1
`StackUtils` `parseLine` method chokes on stack traces containing constructor calls
#69 opened by FUDCo - 0
- 3
Fails to clean all internal Node.js frames
#63 opened by jaydenseric - 1
- 1
document that parseLine can return null
#41 opened by travellingprog - 2
- 1
Need to disable some test on debian
#37 opened by bastien-roucaries - 33
Feature: Support error causes
#61 opened by conartist6 - 1
- 4
What should be considered "internal"?
#8 opened by jamestalmage - 3
Breaking change in v1.0.3
#56 opened by nicolo-ribaudo - 3
stack-utils 1.0.3 causing error in npm test
#57 opened by AnujJain7 - 0
- 6
- 0
Indent option for `clean` method
#12 opened by jamestalmage - 0
Simplify cleaning up immediate dependencies
#15 opened by sindresorhus - 1
- 4
Bikeshed on the API
#1 opened by jamestalmage - 1
- 5
Doesn't clean up `fs` properly
#14 opened by sindresorhus - 2
Tests fail on Node.js master
#26 opened by isaacs - 2
Fail to parseLine when path contains '('
#23 opened by jaridmargolin - 1
- 9
Support promise long stack traces
#2 opened by jamestalmage - 5
license nit
#3 opened by isaacs