Javascript: UNMET PEER DEPENDENCY eslint-plugin-jsx-a11y@^2.2.3

[khankuan]

Hi, I noticed that the version for eslint-plugin-jsx-a11y shows ^3.0.2 but the npm package installed uses ^2.2.3.

[ljharb]

Yes, that is intentional - the package hasn't been updated yet. If you use the npm install command in the readme for eslint-config-airbnb, you'll always get the right peer dependency versions installed.

[khankuan]

Will there be any new releases?

[ljharb]

At some point, certainly. Is there a reason that you need v3 of eslint-plugin-jsx-a11y right now?

[khankuan]

No, just got confused why its out of sync with npm. Thanks for update :)

[khankuan]

And atom starts popping out error: Configuration for rule "jsx-a11y/anchor-has-content" is invalid: Value "" is the wrong type.

[ljharb]

Atom has a bug where you need to restart it when you make any node_modules change.

[khankuan]

Oh interesting, seems like thats the problem. Thanks!

[Aid19801]

I've tried restarting Atom and i'm still getting the same error. Goes away if i switch to Google lint. but unfortunately our team are aligned with AirBnB style. Any ideas how i can fix this relatively quickly?

[ljharb]

@Aid19801 do you have v3 of eslint-plugin-jsx-a11y installed? Our config isn't compatible with that yet - stick to v2.

[UnsungHero97]

@ljharb is a fix for this on the roadmap?

[ljharb]

It's not something that needs fixing - it's just the nature of peer deps in npm - but it's up to v3 on master, so whenever the next release happens, it'll be included.

[Aid19801]

@ljharb thanks mate, will take a look shortly and come back to you.

[ljharb]

Just published v14.0.0 of the main config, and v11.0.1 of the base config.

(#1162, #1166, #1182, #1186, #1207, #1212, #1222)