Support for Eslint v9 Flat Config format

[skyclouds2001]

Here's what I did

config as follows in eslint.config.js

// eslint.config.js
import standard from 'eslint-config-standard'

export default [
  standard,
  // ...
]

this will report:

ConfigError: Config (unnamed): Key "parserOptions": This appears to be in eslintrc format rather than flat config format.

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?

[skyclouds2001]

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')),
  // ...
]

[skyclouds2001]

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',
    ],
  })),
  // ...
]

[53v3n3d4]

This also works

import { FlatCompat } from '@eslint/eslintrc'

const compat = new FlatCompat()

export default [
  // standard,
  ...compat.extends('eslint-config-standard'),

[donalmurtagh]

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
]

[Mtillmann]

Thanks for the solutions. Am I going insane or is eslint completely pointless without support for this package?

[ZelnickB]

It's weird that this is an issue since the README quite literally says that:

This package exports a flat ESLint configuration.

[voxpelli]

@ZelnickB The code in the current repo is not released

[pjg]

@voxpelli could you please release a version with support for the flat eslint config file? It can be a pre-release too, as that also helps.

[voxpelli]

@pjg As mentioned in standard/standard#1948 (comment) an alternative version has been released.

Besides that, I do not know what state the current repository is in as it was modified without my involvement

[skyclouds2001]

Now though the documentation indicates that this repo has supported ESLint flag config, but in fact, this still existed some issues

[whaaaley]

Simply importing packages like FlatCompat or neostandard, not even calling them, completely break vscode eslint extension. We're all in an impossible situation right now for literally 50 lines of code in a config file. Please fix this.

[voxpelli]

@whaaaley neostandard works perfectly with the ESLint extension, and if I wouldn’t be able to make it work there then I for sure wouldn’t be able to make it work here either.

Unless you created an issue about this in neostandard today that I haven’t seen, then this is not something that has been reported to me/us over there.

I myself use the ESLint VS Code extension all the time and with great success, and one of the primary design goals of neostandard was to avoid having to create dedicated extensions, as was needed by standard

[Mtillmann]

@voxpelli would you mind sharing your setup? I have been watching this issue for a long time and I also still have issues getting with vscode. Thanks a lot

[voxpelli]

@Mtillmann I don’t want to hijack this thread too much, questions regarding https://github.com/neostandard/neostandard and its setup I’ll answer there, it’s essentially standard for ESLint 9 with an open governance