Closed JounQin closed 4 months ago
@prettier/plugin-eslint
?prettier-eslint
and prettier-eslint-cli
separately? I would imagine most people use prettier-eslint via the CLI.@lydell
Thanks for your response first!
prettier-eslint
is used by its related VSCode extension with cli, and they're independent for historical reasonprettier
+ eslint
, and eslint-plugin-prettier
requires eslint-config-prettier
as peer. @prettier/plugin-eslint
(the name may be changed) aims to be a prettier plugin but runs eslint after default formatting, it could be a replacement of prettier-eslint
package itself. In this case, all projects are related with each other more or less in my view.eslint-config-prettier
still makes sense, if you're not interested anymore, I can help to maintain it. I'm currently maintaining eslint-plugin-prettier
, prettier-eslint
, prettier-eslint-cli
and working on @prettier/plugin-eslint
.There're other projects like @eslint-stylistic adopting ESLint core stylistic rules, so I think eslint-config-prettier still makes sense
Me too!
if you're not interested anymore
Yeah, now it feels like the config is mostly about disabling stuff in plugins that I don’t use. And I’ve maintained it for 7 years so I’m a bit tired of it.
I can help to maintain it
Feel free to do so! 👍 I’ll be around for questions or help if you need it.
I'm also not interested in dealing with funding. eslint-plugin-prettier
, eslint-config-prettier
, prettier-eslint
and prettier-eslint-cli
are all nice projects in the sense that they have a small and very well defined scope and that doesn't need to change or grow beyond their current states. They're all stable and the only not-negligible feature work is when eslint or prettier release new major versions, which happens about once a year.
Personally I don't feel that level of effort warrants collection of funding. I'd prefer any sponsorship for prettier related things to go towards the core team members that work on the prettier/prettier
codebase itself rather than myself, as I feel that ongoing contributions to prettier itself are much more valuable than my sporadic contributions to eslint-plugin-prettier
and stylelint-prettier
. Being paid for any prettier related work would turn it into an obligation, which would ultimately push me further way from the project - I like my current level of no pay, no obligation, no guilt when I ignore it for a bit.
I feel that projects for specific linter integrations is too niche as I doubt that people would pay to sponsor the slight amounts of work that the projects require.
@BPScott Thanks for your reply first, also!
I'm also not interested in dealing with funding.
That's pretty OK.
Personally I don't feel that level of effort warrants collection of funding.
I'd a bit against about this. Like https://github.com/idahogurl/vs-code-prettier-eslint/issues/200#issuecomment-1848239183, I believe every contribution deserves award. But as I said before, it's totally fine if yourself don't want to be founded. The funding would make the community more health instead of only relying on several maintainers.
I feel that projects for specific linter integrations is too niche as I doubt that people would pay to sponsor the slight amounts of work that the projects require.
Then this will not harm the community neither.
Stale issue
Hi, all!
I know we've been developing independently all together, but I believe we all are using
prettier
+eslint
together, so there must be some common can be share between us.So I just created a brand new OpenCollective project
Prettier ESLint
.I hope we can reach more targets and make
prettier
+eslint
ecosystem better and better.You can point a related OpenCollective project accordingly like:
If you agree, we can share such following
Sponsors
andBackers
table on our project homepage. Of course, feel free to add, remove or sort accordingly to meet your own requirements.Preview:
Sponsors
Backers
Feel free to give me any feedback, agree or disagree, or just want to exit the new OpenCollective project.
cc @BPScott @zimme @kentcdodds @lydell