Open NormandoHall opened 2 weeks ago
There are two issues about integration:
https://github.com/eslint-stylistic/eslint-stylistic/issues/251
https://github.com/eslint-stylistic/eslint-stylistic/issues/218
There are quite a few eslint plugins: https://github.com/dustinspecker/awesome-eslint?tab=readme-ov-file#plugins. It seems hard to decide which we would add, if any. I think the one potential reason for giving this one special treatment is that it used to be a part of eslint core, so it's somewhat popular. Still, it's only about 2% of eslint users that use it and I don't know if it makes sense to add an option that users might say no to 98% of the time. I think the other thing that cuts across this is that there's a small amount of easy setup we can do for the user, but most of the work is configuring it with your exact style rules and that's much too opinionated for us to be able to do by default and so we'd barely be doing any of the work anyway: https://eslint.style/packages/js#install
Thanks for you reply @benmccann . Yes, you are right, but I think this happens because Prettier is "de facto" unopinionated formatter that comes in a lot of frameworks as default. Maybe a good thing would be do a plugin to integrate it as formatter for .svelte
files also.
Well, I leave this as a suggest. Thanks for your work
As Eslint 9 removes all formatters, was a tragedy for all as I who has customized Eslint formatters. Now we have https://eslint.style who has ported all the formatters to a new package. I think it is a good option to offer in SV, "
@stylistic/eslint-plugin
" for alljs/ts
files.Maybe in future we can create a stylistic/svelte plugin to format also
.svelte
files.Here I shared my eslint.config.js file with stylistic formatter if it is useful:
VSCODE settings: