Javascript: latest version of eslint-config-airbnb is not compatible with eslint 7.3.0

Created on 19 Jun 2020 · 7Comments · Source: airbnb/javascript

when using latest version of eslint with latest version of eslint-config-airbnb is throwing the following error:

Oops! Something went wrong! :(

ESLint: 7.3.0

Error: .eslintrc.yml » eslint-config-airbnb » /blablabla/node_modules/eslint-config-airbnb-base/index.js » /blablabla/node_modules/eslint-config-airbnb-base/rules/imports.js:
    Configuration for rule "import/no-cycle" is invalid:
    Value null should be integer.

It seems that when parsing the rule configuration, eslint now receives:

[ 'error', { maxDepth: null, ignoreExternal: false } ]

Removing maxDepth from this line fixes the issue.

needs eslint rule changaddition

Source

nescalante

👍74 😕6

Most helpful comment

Looks like this is due to an eslint bug: https://github.com/eslint/eslint/issues/13427

I'd suggest downgrading to eslint v7.2 for now.

ljharb on 19 Jun 2020

👍11 ❤3

All 7 comments

yes! here's a build failing as you describe

brandly on 19 Jun 2020

I wonder if it has to do with the fact that when you JSON stringify Inifinity it becomes null?

Methuselah96 on 19 Jun 2020

👍5

Looks like this is due to an eslint bug: https://github.com/eslint/eslint/issues/13427

I'd suggest downgrading to eslint v7.2 for now.

ljharb on 19 Jun 2020

👍11 ❤3

v7.2 works as expected. thanks!

brandly on 19 Jun 2020

🎉4

Fixed by ESLint 7.3.1 https://github.com/eslint/eslint/pull/13435

j0k3r on 23 Jun 2020

❤12

They reverted this fix in the new [email protected], until they find a nicer solution. So if you get a similar error, try running it in ESLint 7.3.1 for now.

npm i [email protected]

Knogobert on 9 Jul 2020

No, they reverted the original config cloning change, not the band-aid hack in v7.3.1. v7.4.0 restores the pre-v7.3.0 behavior, so things should work just fine here.