Extract stylistic rules into another eslint plugin

[JounQin]

It could be compatible but deprecate current stylistic rules.

From #186 (comment)

[ota-meshi]

I think the disadvantage of extracting a plugin for stylistic rules is that it makes it a little harder for users to find it.
So far I haven't seen a plugin for stylistic rules exist as a separate plugin in the ESLint plugin ecosystem.

I think the advantage is that there is no need to download stylistic rules, which is not necessary for users who have already introduced the formatter (prettier-plugin-svelte).

[eagerestwolf]

Sorry to stoke an old issue, but this is actually a growing trend in the world of ESLint plugins. There is actually a monorepo where all of the style rules are being moved to. So far, eslint-stylistic has collected the rules from ESLint, @typescript-eslint, and eslint-plugin-react. I think the Vue community is still clinging to their stylistic rules for now. If there is interest within the Svelte team, I could look into extracting the stylistic rules into a package in the eslint-stylistic monorepo (assuming they are also interested), and we could run both for a while to try to encourage the community to switch. Then (assuming it can be done in time), depreciate the rules with Svelte 5, maybe?

[eagerestwolf]

Don't panic about the issue title there. I am just running the idea of adding another package by the eslint-stylistic team before anyone really commits to anything. If they (and you) approve the change, I will work on moving the rules over and everything so that way you guys don't have to worry about it.

[marekdedic]

FWIW, eslint-stylistic now have even in their docs that framework-specific rules are out-of-scope for them. So it would need to be a separate plugin (something like eslint-plugin-svelte-stylistic).

[baseballyama]

This is a matter of decision, but we don’t want to double the maintenance cost by creating a separate plugin at this point. So, we will close this as “won’t do.”