Keep ESLint 10 with React Native plugin compatibility#35
Merged
Conversation
artiphishle
changed the title
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
1 participant
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
@eslint/compateslint-plugin-react-nativewithfixupPluginRules()in the React Native profilebun.lockwith Bun 1.3.13@ankhorage/devtoolsWhy
eslint-plugin-react-native@5still calls deprecated rule-context methods such ascontext.getSourceCode(). ESLint 10 removed those methods, so enablingreact-native/no-inline-stylescrashes during rule initialization before linting can report any inline-style violation.ESLint provides
@eslint/compatspecifically to run plugins that have not yet migrated to the current rule API. Wrapping only the React Native plugin preserves the current ESLint 10 toolchain while avoiding the crash.Impact
React Native and Expo repositories such as ZORA can keep using the latest ESLint 10 line. After this patch is released and consumer lockfiles are updated, React Native rules will run normally. Actual
react-native/no-inline-stylesfindings remain warnings and may still fail repositories that intentionally use--max-warnings=0.