Get non-trivial tests (and trivial, too!) suggested right inside your IDE, so you can code smart, create more value, and stay confident when you push. Learn more →
Why-did-you-render Alternatives
Similar projects and alternatives to why-did-you-render
-
craco
Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
-
react-render-tracker
React render tracker – a tool to discover performance issues related to unintentional re-renders and unmounts
-
Appwrite
Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
-
use-what-changed
A React hook and an easy to use babel-pugin to debug various React official hooks
-
react-devtools
An extension that allows inspection of React component hierarchy in the Chrome and Firefox Developer Tools.
-
razzle
✨ Create server-rendered universal JavaScript applications with no configuration
-
-
CodiumAI
TestGPT | Generating meaningful tests for busy devs. Get non-trivial tests (and trivial, too!) suggested right inside your IDE, so you can code smart, create more value, and stay confident when you push.
-
-
react-styleguidist
Isolated React component development environment with a living style guide
-
RunJS
RunJS is a JavaScript playground for macOS, Windows and Linux. Write code with instant feedback and access to Node.js and browser APIs.
-
-
create-react-app
Set up a modern web app by running one command.
-
Playwright
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
-
eslint-plugin-react
React-specific linting rules for ESLint
-
React-Sight
Visualization tool for React, with support for Fiber, Router (v4), and Redux
-
-
react-native-flash-message
React Native flashbar and top notification alert utility
-
Gatsby
The fastest frontend for the headless web. Build modern websites with React.
-
react-hook-form
📋 React Hooks for form state management and validation (Web + React Native)
-
formik
Build forms in React, without the tears 😭 [Moved to: https://github.com/jaredpalmer/formik]
-
ONLYOFFICE
ONLYOFFICE Docs — document collaboration in your environment. Powerful document editing and collaboration in your app or environment. Ultimate security, API and 30+ ready connectors, SaaS or on-premises
why-did-you-render reviews and mentions
-
After a year developing with react, I think I've been doing all wrong
For debugging why a specific component re-renders, there is also why did you render
-
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
- How do you test number of re-renders?
-
Tools to track re-renders
Couple of questions popped up after discovering this tool called `why-did-you-render`. My understanding is that it helps you keep track of why certain components render.
-
Are there any tools available to help see if useEffect() has a memory leak?
Not exactly what you are looking for (stop runaway effects is it) but this helps diagnose re-renders which can be related: https://github.com/welldone-software/why-did-you-render
-
9 Must-have React Developer Tools to Create Better Apps Faster
The aptly named Why did you render alerts you in the console when an avoidable render occurs. This is a useful attribute to have as it’s not always easy to understand when React components render or rather when they shouldn’t. It’s also an excellent tool for debugging React components, especially if yours is an upstart ReactJS web development team.
-
When developing in React, what do you find most frustrating or cumbersome?
https://github.com/welldone-software/why-did-you-render works pretty well, though I haven't tried it out again in awhile.
-
A note from our sponsor - CodiumAI
codium.ai | 30 May 2023
Stats
welldone-software/why-did-you-render is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of why-did-you-render is JavaScript.
Popular Comparisons
- why-did-you-render VS craco
- why-did-you-render VS use-what-changed
- why-did-you-render VS nextjs-rewrite-test
- why-did-you-render VS react-render-tracker
- why-did-you-render VS react-devtools
- why-did-you-render VS razzle
- why-did-you-render VS MineRender
- why-did-you-render VS RunJS
- why-did-you-render VS react-native-flash-message
- why-did-you-render VS use-context-selector