Before You File a Proposal Please Confirm You Have Done The Following...

• I have searched for related issues and found none that match my proposal.
• I have read the FAQ and my problem is not listed.

Description

In the documentation for the @typescript-eslint/return-await rule, it says that using "in-try-catch" as opposed to "always" is purely a stylistic concern.

However, on this mdn page, it explains in the "Improving stack trace" section that using the "in-try-catch" style results in a worse stack trace. Thus, if true, this is not purely a stylistic concern.

Is this accurate? If so, it seems a compelling reason to use "always" instead of "in-try-catch", and I propose that:

1. the documentation for the return-await rule should be updated to reflect this and
2. the default option should be updated for all users of TSESLint.