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
Support for Eslint v9 Flat Config format #411
Comments
I read https://eslint.org/docs/latest/use/configure/migration-guide#using-eslintrc-configs-in-flat-config and confirmed this way can resolve this issue at present: import path from 'node:path'
import url from 'node:url'
import { FlatCompat } from '@eslint/eslintrc'
export default [
...(new FlatCompat({
baseDirectory: path.dirname(url.fileURLToPath(import.meta.url)),
}).extends('eslint-config-standard')),
// ...
] |
another solution is: import path from 'node:path'
import url from 'node:url'
import { FlatCompat } from '@eslint/eslintrc'
export default [
...(new FlatCompat({
baseDirectory: path.dirname(url.fileURLToPath(import.meta.url)),
}).config({
extends: [
'eslint-config-standard',
],
})),
// ...
] |
This also works import { FlatCompat } from '@eslint/eslintrc'
const compat = new FlatCompat()
export default [
// standard,
...compat.extends('eslint-config-standard'), |
This worked for me import { FlatCompat } from '@eslint/eslintrc'
import { fixupConfigRules } from '@eslint/compat'
const compat = new FlatCompat()
export default [
...fixupConfigRules(
compat.config({
extends: ['standard']
})
)
// other config objects
] |
Thanks for the solutions. Am I going insane or is eslint completely pointless without support for this package? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's what I did
config as follows in eslint.config.js
this will report:
What I expected to happen
should use as above without reporting error
What seems to have happened
it seems that currently eslint-config-standard does not support for flat config format, is there any plan to migrate to flat config format in the future?
The text was updated successfully, but these errors were encountered: