Re-export StackFrame type for backwards compatibility

[andersk]

Description

2.0.7 removed a mis-matching export of StackFrame (#54), but some users were relying on it. Re-export the correct one.

Motivation and Context

#54 (comment)

How Has This Been Tested?

tsc error-stack-parser.d.ts

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• node_modules/.bin/jscs -c .jscsrc error-stack-parser.js passes without errors
  • (You removed jscs in f5184d7.)
• npm test passes without errors
• I have read the contribution guidelines
  • (FYI, this is a broken link when you actually open a PR.)
• I have updated the documentation accordingly
• I have added tests to cover my changes

[eriwen]

Thanks for the PR @andersk!

I'd like to prevent these kinds of regressions using automated checks. Do you have any recommendations (GitHub actions or npm scripts) to do this?

[RenateM]

This commit seems to be causing our builds to fail with the following error:
ERROR in node_modules/error-stack-parser/error-stack-parser.d.ts:9:5 - error TS1128: Declaration or statement expected.
9 export type {StackFrame};
~~~~~~
node_modules/error-stack-parser/error-stack-parser.d.ts:9:17 - error TS1005: ';' expected.
9 export type {StackFrame};
~

[andersk]

@RenateM It sounds like you have a very old version of TypeScript. Make sure you’ve upgraded to at least 3.8 (latest: 4.7.3).