The number of rerenders are actually correct. Let's analyze what happens:

1. Rendering 0 - this is on mount first render (in this state, every useEffect is run automatically)

2. Triggered 0 - this is initial triggering of useEffect

3. Rendering 4 - this rerender is because you set new state of index to 4

4. Triggered 4 - this is triggered because you changed index from 0 to 4

5. Rendering 4 - this is run because state is changed from 4 to 4 (even the value is the same, it will trigger component rerender because React does not know if you set same state, and it needs to run again). In this rerender useEffect is not run because index is 4 again.

Rationale

If anything changes in a component at any point like useState useContext, customHook, that component will need to rerender. This also happens if the parent component rerenders, child component will rerender even if your component did not have any changes.

Additional rerendering tips and info

To prevent parent unnecessary rerendering of child components from happening you can use React.memo, this will rerender your component if props change, but wont prevent your component from rerendering if state or any of the above hooks change in there.

If this seems redundant, it sounds like it, but it is necessary so that react is sure it has the latest state. Running JS like this is faster than having some state memory that checks changes and also it is more transparent for the developer (and just how the VDOM is created)

Expected output can't be achieved.

useEffect renders on when component mount and on every re-render when state changes(index).

const Example = () => {
    const [index, setIndex] = React.useState(0)
    console.log('Rendering: ', index)
    React.useEffect(() => {
        console.log('Triggered: ', index)
        setIndex(4)
    }, [index])

    return <h1>{index}</h1>
}

Output:

• Rendering: 0 => When component mount first time, that time index is 0
• Triggered: 0 => On mount useEffect triggers, and state updated(0 to 4)
• Rendering: 4 => Componet re-rendered because state has changed from (0 to 4)
• Triggered: 4 => useEffect re-triggered because state has changed(0 to 4)
• Rendering: 4 => Componet re-rendered because to check whether state has changed or not (4 to 4, kind of confirmation nothing changed )

The way useEffect work is it only runs after page component is rendered.

Hope this will help you to understand.

1st render index is 0.

Rendering:  0

It triggers the useEffect.

Triggered:  0

Index is updated in the useEffect but not in the component. Then render updates the index to 4.

Rendering:  4

The useEffect runs because index has changed.

Triggered:  4

The component is rendered again but index is still 4 so the useEffect wont run again.

Rendering:  4