One uses both bluebird and Q to generate promise long stack traces with From previous event: lines.
The other uses nested-error-stacks to create long stack traces with Caused By... lines.
Indentation is removed from all lines until the first separator line is found.
If all at lines are removed in a given section, then the separator line is also removed (not sure if this is the right thing to do, but I think it is).
Fixes #2
This creates two sets of fixtures:
bluebirdandQto generate promise long stack traces withFrom previous event:lines.nested-error-stacksto create long stack traces withCaused By...lines.Indentation is removed from all lines until the first separator line is found.
If all
atlines are removed in a given section, then the separator line is also removed (not sure if this is the right thing to do, but I think it is).Reviewers: @isaacs @sindresorhus