payment-split
why-did-you-render
| payment-split | why-did-you-render | |
|---|---|---|
| 4 | 47 | |
| 6 | 10,825 | |
| - | 0.8% | |
| 4.3 | 7.1 | |
| 11 months ago | 16 days ago | |
| TypeScript | JavaScript | |
| - | 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.
payment-split
- Free code review
-
Thinking about starting a open source project
I made splitwise like app in React (+ Typescript) if you wanna contribute some features to it. https://github.com/swport/payment-split
-
First React side project I finished all the way
Repo: https://github.com/swport/payment-split
-
First side project I finally completed (almost)
Give the repo a star if you liked it. Thanks.
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?
chatter
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
pokeinfo
use-what-changed - A React hook and an easy to use babel-pugin to debug various React official hooks
react-native-swipeable-deck - A swipe deck for react native in simular style as tinder
nextjs-rewrite-test
shop-react
react-render-tracker - React render tracker – a tool to discover performance issues related to unintentional re-renders and unmounts
react-ts-vite-template - React TypeScript template with Vite
react-devtools - An extension that allows inspection of React component hierarchy in the Chrome and Firefox Developer Tools.
constitution-project
razzle - ✨ Create server-rendered universal JavaScript applications with no configuration