Already publish flat config version?

[JiangWeixian]

Already publish flat config version?

[mightyiam]

Sorry. @geekytime is correct. We (I, @rostislav-simonik and @jay-bulk) simply don't have the npm permissions necessary to do this yet.

[mightyiam]

To publish this package, that is.

[EliRobinson]

While we wait patiently for this to come true, has anyone figured out a workaround to bypass the parserOptions errors?

[mightyiam]

Just wanted to let those following know that I no longer participate here, because I was never granted the trust of the original author.

I took my work to eslint-config-love.

[geekytime]

It looks like the flat config is available on the master branch, so it's the default in the docs, but it hasn't been published, yet. I think the @latest published version is still the old-style config.

[jaridmargolin]

@mightyiam - Is there any interest in tagging/creating a git release so folks can still use the new config via a github URL?

[mightyiam]

@mcollina we need publish permissions.

[JamiesonRoberts]

Any update on this? Or getting in contact with a maintainer that can either grant permissions or publish to NPM?

Another thought: should probably setup automatic deployment to NPM on a release creation via GitHub, that way it avoids this issue in the future

[mightyiam]

standard/standard#1948

[donalmurtagh]

While we wait patiently for this to come true, has anyone figured out a workaround to bypass the parserOptions errors?

Yes!

It's possible to make the current version work in an ESLint v9 flag configuration file using @eslint/compat by following these instructions.

In my case I made these changes to eslint.config.js

import { FlatCompat } from '@eslint/eslintrc'
import { fixupConfigRules } from '@eslint/compat'

const compat = new FlatCompat()

export default [
  ...fixupConfigRules(
    compat.config({
      extends: ['standard']
    })
  ),
  // other config objects
]