I'm not only the author of @prettier/plugin-pug, a core member of Vite as well as a core maintainer of Faker, but I also contributed already with https://github.com/Shinigami92/eslint-define-config to the eslint ecosystem as well as a collection of other projects:

• https://github.com/typescript-eslint/typescript-eslint/issues?q=author%3AShinigami92+
• https://github.com/gajus/eslint-plugin-jsdoc/issues?q=author%3AShinigami92+
• https://github.com/vuejs/eslint-plugin-vue/issues?q=author%3AShinigami92+
• https://github.com/vuejs/vue-eslint-parser/issues?q=author%3AShinigami92+
• https://github.com/veritem/eslint-plugin-vitest/issues?q=author%3AShinigami92+
• https://github.com/muenzpraeger/eslint-plugin-inclusive-language/issues?q=author%3AShinigami92+

That's why I want to raise my hand and offer help, as long as it fits into my time frame and I gain fun out of contributing to the community

@antfu - I enjoyed your prolific use of ESLint when working on UnoCSS and now I too use it solely. At first I tried adopting your default config but there's a ton of Vue stuff in there that's irrelevant for Svelte and all the Svelte rules are obviously not in there so I started from scratch. I'm still pretty fresh in this arena but I use the new flat config (eslint.config.js) and ideas from you. I love it, and would be willing to be a tester in the Svelte context for whatever comes of this package as I'm sure it will be helpful.