Support for the new FlatConfig format

[AndreaPontrandolfo]

Any plans to support the new Eslint FlatConfig format, eslint.config.js?
In the next major release of Eslint, the new format is gonna be the default and the old format deprecated, so it should be updated.

[jaydenseric]

The most obvious thing that needs to happen is to publish TypeScript typings for the package, so that you can programmatically import and use this ESLint plugin with type safety when your eslint.config.js file is type-checked:

// @ts-check

// Currently `any` :(
// Even worse, it's actually a TypeScript error if `compilerOptions.moduleResolution`
// is configured to `bundler` instead of `nodenext`, about there being no default export.
import eslintPluginStorybook from "eslint-plugin-storybook";

[yannbf]

Hey there! Thanks for opening this issue.

Are you willing to contribute to make this happen? I'm happy to guide in the process if needed!

[waldemarfm]

@yannbf I'm interested in helping with this. I don't think it'll be too complicated.

Would the approach be a major version bump and go all in on the change, or do we somehow offer support for both formats and make it opt-in for projects using flag configs?

[AndreaPontrandolfo]

I would love to contribute but i also have my hands-full with OSS projects right now.

[yannbf]

Hey @AndreaPontrandolfo @waldemarfm contributions are definitely welcome. If this change can be done in a backwards compatible way, that'd be definitely preferred! If you know what are the steps to support this format, describing those would already be quite helpful as well!

[mheob]

Some more information: Plugin Migration to Flat Config - ESLint