`jsx-a11y/href-no-hash` removal
See original GitHub issueHello. jsx-a11y/href-no-hash
has been removed/renamed a few days ago, and your rule is now raising errors
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:26
Top Results From Across the Web
Fix to : Links must not point to “#”. Use a more descriptive href ...
Getting warning: Links must not point to "#". Use a more descriptive href or use a button instead jsx-a11y/href-no-hash While its only a ......
Read more >Disabling specific eslint rules - DEV Community
The create react app eslint presets come with a few rules that are slightly annoying. One of them is jsx-a11y/href-no-hash, which makes sure ......
Read more >Disable warning message for eslint rule not being found
I'm working on getting eslint working in my app for the first time. I have it mostly working, but since I've started disabling...
Read more >eslint-plugin-jsx-a11y - npm
This plugin does a static evaluation of the JSX to spot accessibility issues in React apps. Because it only catches errors in static...
Read more >eslint-plugin-jsx-a11y | Yarn - Package Manager
1 / 2022-07-21. 38405ad [Fix] no-interactive-tabindex : allow role assignments using a ternary with literals on both sides; 7524e0c [Fix] ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@TrejGun that’s because we aren’t compatible with v6 of
eslint-plugin-jsx-a11y
- if you runnpm ls
you’ll see that your dependencies are invalid, which means that you can’t expect anything to work. Downgrade that plugin to v5, and everything will work (or just use the install command in the eslint-config-airbnb readme in the first place, which every single person commenting in this thread after it was closed also failed to do)There’s an existing issue; it might have been mistakenly closed.