RFC: Move stylelint-prettier to the prettier organization

Hi folks, I’m opening this here as I’m not sure where else to ask.

I maintain stylelint-prettier which exposes prettier changes a within stylelint, in the same way that eslint-plugin-prettier exposes prettier changes within eslint. I’ve been using this for about two months at work without issue, and I consider it stable and feature-complete (baring one or two possible bugs around processing CSS in custom filetypes).

Given that eslint-plugin-prettier, eslint-config-prettier and stylelint-config-prettier are all part of the prettier organization I was wondering if the prettier team would be interested in having stylelint-prettier be housed under the prettier organization too?

[lipis]

So I think we can close that issue now.

[BPScott]

Shall we rename it to prettier-stylelint maybe?

No, it’s a plugin for stylelint, and their convention is to name plugins stylelint-THING. prettier-stylelint would be a tool that runs prettier then stylelint.

This is consistent with how the eslint tooling is named:

eslint-plugin-prettier: A plugin for ESLint (as their conventions say to prefix the package name with eslint-plugin). prettier-eslint: A tool that runs prettier --write then eslint --fix over a file.