chore: gitignore regenerated .eslintrc.js#7
Merged
Conversation
expo-module-scripts' configure step (run by the prepare lifecycle) recreates a legacy .eslintrc.js from its template whenever the file is missing. The project uses ESLint flat config (eslint.config.js), so the regenerated file is inert and not part of the published tarball — ignore it to keep it out of git.
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.
What
expo-module-scripts'configurestep (run by thepreparelifecycle on everynpm install) recreates a legacy.eslintrc.jsfrom its template whenever the file is missing. This project uses ESLint flat config (eslint.config.js), so the regenerated file is inert (ESLint 9 ignores it) and isn't part of the published tarball.Ignoring it keeps the regenerated file out of git after a fresh install.