Revert to @babel/eslint-parser in eslint-config #47333
Closed
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.
Summary:
Motivated by facebook/hermes#1549. This was originally changed in #46696, as our internal Flow support had diverged from
babel/eslint-parser
(#46601).We effectively have three flavours of JavaScript in support:
react-native
package, shipped as source — useshermes-parser
.babel/plugin-syntax-typescript
.babel/plugin-syntax-flow
viababel/eslint-parser
(this change).I'd love to simplify this 😅.
Switching to
hermes-eslint
for the RN monorepo codebase (D63541483) is unchanged.Changelog: [Internal]
Reviewed By: cipolleschi
Differential Revision: D65272156