'jsx-a11y/href-no-hash' was not found jsx-a11y/href-no-hash

Is this a bug report?

yes

Can you also reproduce the problem with npm 4.x?

yes

Environment

1. node -v: 8.9.0
2. npm -v: 5.5.1
3. yarn --version (if you use Yarn): 1.3.2
4. npm ls react-scripts (if you haven’t ejected): react-scripts@1.0.17

Then, specify:

1. Operating system: mac os 10.13.1
2. Browser and version (if relevant):

Steps to Reproduce

(Write your steps here:)

1. after update
2. yarn start

Expected Behavior

No warnings!

Actual Behavior

after update to 1.0.17 warning in all file in project @#

Reproducible Demo

no

[gaearon]

That’s the problem:

"eslint": "^4.10.0",
"eslint-config-airbnb": "^16.1.0",
"eslint-config-prettier": "^2.7.0",
"eslint-plugin-import": "^2.7.0",
"eslint-plugin-jsx-a11y": "^6.0.2",
"eslint-plugin-prettier": "^2.2.0",
"eslint-plugin-react": "^7.4.0",

Using custom ESLint configs with CRA projects is not supported and is subject to issues like this. In particular, the difference in eslint-plugin-jsx-a11y versions is causing the trouble.

[gaearon]

Of course if you eject you can customize anything you want.

But you can’t expect that you can take two arbitrary ESLint presets and use them together. If they rely on different versions of plugins, you need to either pick just one of them, or wait for them both to “line up”.

We try to keep up with the updates, but we don’t always match what Airbnb preset uses. If you ejected and prefer Airbnb’s preset, just remove ours.