feat(eslint-config)!: change return-await rule to always enforce usage#200
Open
CptSchnitz wants to merge 1 commit into
Open
feat(eslint-config)!: change return-await rule to always enforce usage#200CptSchnitz wants to merge 1 commit into
CptSchnitz wants to merge 1 commit into
Conversation
syncush
approved these changes
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes:
Updates the central ESLint configuration file to enforce "@typescript-eslint/return-await": "always".
Why:
Zero-cost async stack traces: We get full, accurate stack traces when a returned promise rejects.
Prevents try/catch bugs: Eliminates the trap where a developer wraps a return promise in a try/catch, but the catch fails to fire because the promise wasn't awaited.
No performance penalty: Modern V8 natively handles return await without the historical microtask overhead.
Consuming projects will see linting errors for any un-awaited promises returned from async functions. These can be safely auto-resolved by running eslint --fix on the consuming codebase.