Skip to content

Conversation

@PyvesB
Copy link
Member

@PyvesB PyvesB commented Oct 19, 2025

Continuing the dependency audit started in #11425.

According to its README, eslint-config-prettier:

Turns off all rules that are unnecessary or might conflict with Prettier.

Sure, that sounds potentially useful on paper. But we're no actually using that plugin directly, it isn't added to our ESLint configuration file. We're leveraging eslint-plugin-prettier/recommended, that brings in a sane config.

@PyvesB PyvesB added the dependencies Related to dependency updates label Oct 19, 2025
@github-actions
Copy link
Contributor

Messages
📖 ✨ Thanks for your contribution to Shields, @PyvesB!

Generated by 🚫 dangerJS against d6f2a1c

Copy link
Member

@jNullj jNullj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still use the config, as it's loaded from the plugin.
It's both added as a dependency and also mentioned on this section of the readme that eslint-plugin-prettier loads eslint-config-prettier.

But as you mentioned, we don't call this directly, a more proper way may be letting npm install eslint-config-prettier without explicitly making it one of our dev dependencies.

@PyvesB
Copy link
Member Author

PyvesB commented Oct 21, 2025

Indeed! But yeah, what I meant is that we should not need to worry, what config eslint-plugin-prettier/recommended pulls in is an implementation detail. :)

@PyvesB PyvesB added this pull request to the merge queue Oct 21, 2025
Merged via the queue into badges:master with commit a2edbf5 Oct 21, 2025
22 checks passed
@PyvesB PyvesB deleted the drop-eslint-config-prettier branch October 21, 2025 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Related to dependency updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants