pretty-quick
eslint-plugin-jsx-a11y
pretty-quick | eslint-plugin-jsx-a11y | |
---|---|---|
6 | 17 | |
2,173 | 3,326 | |
0.4% | 0.6% | |
6.8 | 7.1 | |
26 days ago | 21 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pretty-quick
-
npx looking first in the global cache and not local project node_modules
recently my team started facing this issue about pretty-quick not compatible with [[email protected]](mailto:[email protected]). (https://github.com/azz/pretty-quick/issues/164)
-
Setting up ESLint & Prettier in ViteJS
If you'd like, you can go a bit further and automate the linting and formatting process a bit. I like to use Husky which allows you to run your linter, tests etc. on a git commit/push etc. You can also then use pretty-quick along with husky to automatically format your code whenever you git commit, just in case someone on your team hasn't set it up in their IDE.
-
How to properly set up Prettier in less than 2 minutes
By using husky and pretty-quick, you can automatically force every developer to format all the changed files (and nothing more) every time they commit.
-
Adding Prettier to a Project
Set up commit hooks with pretty-quick and husky. First, install them as dev dependencies:
-
Awesome Dev Tools To Automate Code Tasks 🔥
In this tutorial, we will also use commitlint and pretty-quick libs to check if your commit messages meet the conventional commit format and run prettier on changed files respectively.
-
How to set Husky
So basically husky is "Git hooks made easy" and we are going to use to automatically format all of our code that is staged for our commits, so we are going to use the "pre-commit" hook to run pretty-quick a simpler way to run our prettier scripts with configuration
eslint-plugin-jsx-a11y
- Tailwind Handbook - Part II
-
Speeding up the JavaScript ecosystem – Polyfills gone rogue
I try to focus on the issues rather than individuals, but the root of the problems in the listed eslint plugin libraries points to ljharb.
If you do some simple digging into these libraries, you will find that these types of commits are quite common within them.
https://github.com/jsx-eslint/eslint-plugin-react/commit/e1d...
https://github.com/jsx-eslint/jsx-ast-utils/commit/bad51d062...
https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/commit/...
He would rather see the download count of these polyfill libraries https://github.com/ljharb/ljharb#projects-i-maintain increase, compared to assessing the health of the JavaScript ecosystem.
-
The Best ESLint Rules for React Projects
jsx-a11y is all about ensuring your DOM elements are accessible. This plugin will prompt you to include the correct ARIA attributes such as labels and roles, in addition to things like alt text.
-
Create React UI Lib 1.1: Ladle and ESLint
You can also add ESLint now (props to @femincan for the suggestion). It comes with recommended settings for these plugins: typescript, prettier, react, react-hooks, jsx-a11y.
-
Light UI component library but as good as MUI (or atleast close to it)?
WAI-ARIA is important if you are writing custom components and do not follow the general rules for HTML tags. For example, if you are using a `div` as a button, you would need to add tags for accessibility. Yes, there are some other instances, like adding alt text to images or adding a title to an iframe, but these can all be handled with warnings in the editor using the jsx-a11y eslint plugin. Some other nuance will be up to the developer to make sure they follow the proper accessibility structure, but most use cases are outlined in the Daisy UI tailwind examples, they do a great job of using HTML properly and give fully accessible examples for their components. Take a look at the accordion example, you can tab into the accordion and use the arrow keys to navigate.
-
Introducing react.dev: the new React docs site!
jsx-a11 (ESLint plugin) checks a couple other things.
-
Newbie question about ARIA/ADA Compliance
When using react, I've been using the recommended rules from eslint-plugin-jsx-a11y. Am I naive for relying a lot on that to get a11y right? Of course I try to write semantic html too and do research for each topic, but it's a bit overwhelming and I feel like the eslint rules help me a lot.
-
Can someone help me locate documentation where this eslint rule is talked about?
I found the documentation but no solution here: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/label-has-associated-control.md
-
Setting up ESLint & Prettier in ViteJS
eslint-plugin-jsx-a11y: Checks for accessiblity issues.
-
Introduction to Web Accessibility (A11Y)
For example, Deque's open-source Axe project can help identify issues such as common HTML semantic errors, contrast problems, and more. There are even libraries that help integrate Axe into your project's linters, such as one for React called eslint-plugin-jsx-a11y.
What are some alternatives?
prettier - Prettier is an opinionated code formatter.
chakra-ui - ⚡️ Simple, Modular & Accessible UI Components for your React Applications
husky - Git hooks made easy 🐶 woof!
jest-axe - Custom Jest matcher for aXe for testing accessibility ♿️🃏
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
svelte-navigator - Simple, accessible routing for Svelte
commitlint - 📓 Lint commit messages
vite - Next generation frontend tooling. It's fast!
prettier-java - Prettier Java Plugin
agnostic-axe - Framework agnostic accessibility reporter, powered by axe-core
prettier-eslint-cli - CLI for prettier-eslint
react-a11y-announcer - React Announcer for Screen Reader Accessibility