eslint-plugin-jsx-a11y
why-did-you-render
| eslint-plugin-jsx-a11y | why-did-you-render | |
|---|---|---|
| 2 | 47 | |
| 2,594 | 10,841 | |
| - | 1.0% | |
| 7.5 | 7.1 | |
| over 2 years ago | 21 days ago | |
| JavaScript | 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.
eslint-plugin-jsx-a11y
-
A control must be associated with a text label
As pointed out by @rickdenhaan, the correct rule to apply is this one.
-
Awesome React Resources
eslint-plugin-jsx-a11y - Static AST checker for a11y rules on JSX elements
why-did-you-render
- Too many rerenders in react?
- Lag issues with RN
- After a year developing with react, I think I've been doing all wrong
- How can I stop a component from reloading all the time?.
-
How to speed up React Native screen when full of TextInput?
Check out why-did-you-render. It may tell you some more information.
-
Why and How We Retired Elm at Culture Amp
It's a combination of many things, but imo one of the worst is all the footguns regarding state and the rerenders they cause
https://emnudge.dev/blog/react-hostage
It's so easy, that we monkey patch react to debug it https://github.com/welldone-software/why-did-you-render
Plus the vdom... Isn't great, the bundle size puts react at an inherit disadvantage, and the community has a knack for over reliance on bloated packages
-
7 Proven Practices to Boost Development Speed and Project Quality
When we implemented the MVP of the fintech app, we had a quite complicated form. At that time, I was still young and inexperienced. And eventually, we realized that our project was slowing down. We had to spend additional hours figuring out the reason. We had many unnecessary re-renders because we ignored basic rules related to props in React. I wanted to do everything possible to avoid such situations in the future. So, I added to the project linters like this and an additional starting configuration to package.json to run why-did-you-render. In short, this plugin issues a warning if something is re-rendered unnecessarily and suggests how to avoid it. Also, we included running Lighthouse in headless mode. Some people say that premature optimizations are bad, but for me, it's a principle: do it right from the start.
- Free code review
-
Is there a way to detect unwanted mutations in a React component?
maybe somethin like https://github.com/welldone-software/why-did-you-render
-
React Dev Tools: much worse experience with functions/hooks
This might help you out a bit.
What are some alternatives?
react-a11y-announcer - React Announcer for Screen Reader Accessibility
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
eslint-plugin-react - React-specific linting rules for ESLint
use-what-changed - A React hook and an easy to use babel-pugin to debug various React official hooks
a11y-twitter - Small changes to how you use Twitter to promote Tweeting in an accessible manner. For now, it will only prompt once per Tweet to add alt text to an attachment before you Tweet. Simple but effective. 😎
nextjs-rewrite-test
react-loadable - :hourglass_flowing_sand: A higher order component for loading components with promises.
react-render-tracker - React render tracker – a tool to discover performance issues related to unintentional re-renders and unmounts
create-react-library - CLI for creating reusable react libraries.
react-devtools - An extension that allows inspection of React component hierarchy in the Chrome and Firefox Developer Tools.
react-fiber-architecture - A description of React's new core algorithm, React Fiber
razzle - ✨ Create server-rendered universal JavaScript applications with no configuration