State Persists Between Renders
What you'll learn: Why state values survive re-renders while regular variables reset every time.
The Problem with Regular Variables
When a component re-renders (because props change, state updates, or a parent re-renders), React calls your component function again from scratch. Any regular variables you declare get re-initialized to their starting values:
function Counter() {
let count = 0; // Resets to 0 every render!
return (
<button onClick={() => {
count = count + 1; // Changes local variable...
console.log(count); // ...but doesn't trigger re-render
}}>
Count: {count}
</button>
);
}
The button will always show "Count: 0" because count gets recreated as 0 on every render.
How State is Different
When you use useState, React stores the value outside your component function. Think of it like React keeping a special notebook where it writes down your state values and remembers them between function calls:
function Counter() {
const [count, setCount] = useState(0); // React remembers this!
return (
<button onClick={() => setCount(count + 1)}>
Count: {count}
</button>
);
}
Now the button works! When setCount is called:
- React updates its internal notebook
- React triggers a re-render
- Your function runs again
useStatereturns the remembered value, not the initial value
The Analogy
Regular variables are like writing on a whiteboard that gets erased before each render. State is like writing in React's permanent ledger that survives between renders.
Key Takeaway: State persists across re-renders because React stores it separately from your component function, while regular variables get reset every time the function runs.