Ditch eslint-plugin-prettier and use eslint-config-prettier#3910
Merged
Conversation
- We don't need `eslint-plugin-prettier` since we use Prettier as a formatter. Moreover, it conflicts with the specified rules since it doesn't consider our Prettier configuration. - Use `eslint-config-prettier` to turn off all unnecessary rules that might conflict with Prettier.
✅ Deploy Preview for dev-prismjs-com ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
LeaVerou
approved these changes
Apr 27, 2025
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.
eslint-plugin-prettiersince we now use Prettier as a formatter. Moreover, it conflicts with the specified rules because it doesn't consider our Prettier configuration.eslint-config-prettierto turn off all unnecessary rules that might conflict with Prettier.