-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export flat configs from root entry point #135
Conversation
Now access to flat config from root of the module.
Hi, thanks for putting this together. I'd like to dig into the idea that "most plugins export their flat configs from the root entry point" a little bit more.
All this to say, I'm not certain that a true standard has emerged about whether to use My personal opinion is that I do feel like there's a compromise position. I'll plan to keep the recommendation the same, but will add const pluginLegacy = {
rules: plugin.rules,
configs: [
recommended: { /* ... */ },
typescript: { /* ... */ },
'flat/recommended': recommendedConfig,
'flat/typescript': typescriptConfig,
}
export = pluginLegacy; and add a note that the flat configs are available at |
@joshwilsonvu Can you handle these two commits as well?: If it's too difficult, I'll create a separate PR. Please let me know your thoughts :) |
As described here, most other plugins that support flat configs export their flat configs from the root entry point. Therefore, to avoid confusion among users, this plugin also exports its flat configs from the root entry point.
Accordingly, I updated the README and deprecated the previous entry points.