Support of new eslint flat config

[OlivierZal]

Hi,

eslint.config.js should be added in

javascript/packages/eslint-config-airbnb-base/rules/imports.js

Line 94 in cda44da

'**/.eslintrc.js' // eslint config

in order to support new eslint flat config.

Thanks!

[ljharb]

sadly yes, that's true.

[OlivierZal]

I can do the PR if you want, is there a release branch?

[ljharb]

Actually we may need to wait until all of our peer deps support flat config. If that’s already working, then a PR to the default branch is fine.

[Krushna-Nanda]

how should i contribute , where to start

[OlivierZal]

@ljharb, I don't know the exact process on this project, but here's a PR from a fork: https://github.com/airbnb/javascript/pull/2818/files

[filiptammergard]

A PR for adding eslint.config.js is up: #2849

You can already use flat config, even when using plugins and configs that don't yet support it, by using ...compat: https://eslint.org/docs/latest/use/configure/migration-guide#using-eslintrc-configs-in-flat-config Many project already do this.

I don't think we need to wait for full flat config support to allow importing dev dependencies from flat config files.

[sergeushenecz]

After upgrade to eslint 9.0.0. now i see error
I used ...compat.extends('airbnb'), and all was ok.
But now i see
Error: Failed to load config "airbnb" to extend from.
Maybe someone know how does it fix?

[sergeushenecz]

is this library not suported ?

[OlivierZal]

Every config needs to be updated to support new v9 eslint API, which has breaking changes.

Since v9 has been released yesterday, we probably need to wait for configs’ compatibility (see eslint/typescript, which has a dedicated issue with thread about it and tracking).

[ljharb]

Correct; just like with every eslint major, all the plugins this config depends on have to support it before we can.

[adrian-gierakowski]

For reference, tracking issues for plugins which need to be resolved first:

import-js/eslint-plugin-import#2556

jsx-eslint/eslint-plugin-react#3699
jsx-eslint/eslint-plugin-react#3685

jsx-eslint/eslint-plugin-jsx-a11y#978

@ljharb have I missed anything?

[ljharb]

eslint-find-rules, as well.

[iserdmi]

Hello! Have we got any expectation when approximately airbnb flatconfig will be ready? Some days, weeks, or months?

[ljharb]

@iserdmi nope. in the past it's taken multiple months to support a new eslint major, but this one is more disruptive and difficult to migrate to, so it might take longer.

[efoken]

@ljharb I think this issue is only about adding eslint.config.js inside import/no-extraneous-dependencies and not about implementing flat config. I am already using eslint.config.js with the Airbnb config (with compat) and I had to disable this rule because of that

[ljharb]

@efoken you shouldn't be using flat config with this plugin at all until we actually support it.

[efoken]

@ljharb as long as people use ESLint 8 with flat config and use the Airbnb config with compat there isn't any problem, everything works perfect 😉

[farski]

Sorry if this is all very obvious, and I'm just not understanding it. It seems like there are several possible (theoretical) scenarios:

1. Using eslint-config-airbnb ESLint 8 with legacy config
2. Using eslint-config-airbnb ESLint 8 with flat config via FlatCompat
3. Using eslint-config-airbnb ESLint 8 with flat config (no FlatCompat)
4. Using eslint-config-airbnb ESLint 9 with legacy config (ESLINT_USE_FLAT_CONFIG=false)
5. Using eslint-config-airbnb ESLint 9 with flat config via FlatCompat
6. Using eslint-config-airbnb ESLint 9 with flat config (no FlatCompat)

I believe the ultimate goal is № 6. Based on the @efoken's comment above, it seems like № 3 also works. Is there a benefit to switching to flat config on ESLint 8, other than a slightly smoother upgrade to ESLint 9 down the road? And is it true that neither № 4 or № 5 work?

[ljharb]

1 is already possible, obviously.

2 and 5 might work, but neither eslint nor myself will likely be able to effectively support you, so you're kind of on your own with those.

This issue tracks number 3 (and unblocks 6, once 4 is achievable). Number 4 (and thus 6) is tracked in #2961.