← Back to list

Avoid too many useStates in React — Fix unnecessary rerenders

I’ve been making such a mistake for a very long time. Any value that changed instantly joined the state. It was similar to the React…

DevManus · 2026-01-07 16:30 · 0 claps · 1.7 min read
#usestate #react-state #rerender #state-management #react-form-handling
Open on Medium ↗
Wiki topics: BIZ · Business Strategy 🌐 · Web Development

Avoid too many useStates in React — Fix unnecessary rerenders

I’ve been making such a mistake for a very long time. Any value that changed instantly joined the state. It was similar to the React method. However, as the app grew, it became more difficult to forget about its drawbacks.

A re-render is not necessary for every value. React ends up doing more work than is necessary while everything is in state. Even when there is no real reason to change the user interface, components re-render. This eventually causes performance problems that are difficult to link to a single line of code.

Additionally, I faced stale closure problems several times. State changes, particularly inside effects and event handlers, didn’t act as I thought they would.

Bad Code Example:

Fix Code Version :


메타데이터
post_id
6510c3d0bef4
slug
avoid-too-many-usestates-in-react-fix-unnecessary-rerenders-6510c3d0bef4
url
https://medium.com/@DEVManus49/avoid-too-many-usestates-in-react-fix-unnecessary-rerenders-6510c3d0bef4
canonical_url
https://medium.com/@DEVManus49/avoid-too-many-usestates-in-react-fix-unnecessary-rerenders-6510c3d0bef4
author_url
https://medium.com/@DEVManus49
status
ok
fetched_at
2026-08-22 01:25:53