chore: remove unused eslintConfig
#620
Merged
Conversation
This file contains 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
privatenumber
changed the title
eslintConfig
|
Good catch, this should've been removed. The config is just passed in as CLI flags to |
|
This issue is now resolved in v4.16.3. If you're able to, your sponsorship would be very much appreciated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Putting the ESLint config in
eslint.config.jsmakes it discoverable by editor integrations so that they can show lint errors/fixes inline.AFAICT
lintrollcompletely ignores theeslintConfigproperty inpackage.json, so it already wasn't necessary (and there wasn't a@pvtnbr/*package installed to begin with). The ignore oftests/fixtures, despite being ignored in the first place, also just isn't necessary.