⚛️ React optimization tip: break your context into chunks so only the updated parts re-render ↓

I've been working professionally with React for more than 8 years and I compiled all my knowledge into 100+ infographics and 70+ video tutorials just like this one. Check them out ↓

This is the biggest productivity cheat code right now. Kiss reading documents goodbye. You can get an instant summary of any document with this tool.

or use react compiler

This is an essential technique when scaling React applications. You could end up with a large tree of components updating due to a small state change.

Smaller contexts ⇒ Less reasons to change and rerender.

@Rhoy__b @ibr9heem

you can also have separate context for methods and states to optimise it even more. I saw that implemented in bluesky app.

Will this remain relevant with the React compiler?

Make one to optimise compound components. Despite memorizing referrence values and using callbacks for functions, i sometimes see a flicker

What theme is it?

I would personally avoid to use Context as much as possibile I explain my approach in this article