Open JoshuaKGoldberg opened 3 months ago
😎 Thanks for filing @JoshuaKGoldberg !! ... I think you've been working with @Tobbe on this already? Anything else you need from us?
Awesome, thanks @ahaywood!
Digging into the code, it looks like there are two things we could mean by "flat config support":
@redwoodjs/eslint-config
: switching it to use the flat config format@redwoodjs/eslint-plugin
: getting it to export plugin metadataThe 🍎 config would be a lot more work, as it's got a lot of dependencies & listings that'd need to switch. I don't think I'm well-positioned as a first-time external contributor to do that.
But the 🍌 I'd be happy to. It's common for ESLint plugins to also export a "recommended" ruleset - doing that here would be a happy point. So if you don't mind, I just renamed this issue, will file a new one for the plugin, & can work on that now.
What's not working?
👋 Coming over from https://github.com/eslint/eslint/issues/18093: ESLint is migrating to a new "flat config" format that will be the default in ESLint v9.
It doesn't look like
@redwoodjs/eslint-config
has support yet. I'm posting this issue here as a reference & cross-linking it to the table in https://github.com/eslint/eslint/issues/18093. If there's anything technical blocking the extension from supporting flat configs, please let us know - we'd be happy to try to help! 💜Additional resources:
How do we reproduce the bug?
npm i @redwoodjs/eslint-config eslint -D
eslint.config.js
with... well, there's no actual exported config from@redwoodjs/eslint-config
to use there!Just for fun, I tried out:
...but
npx eslint
fails on that with:What's your environment? (If it applies)
Are you interested in working on this?