Thx, for the article. But there's 2 things you probably should to worry about (especially if you want to use it in production for big applications):
When you write code like <Provider value={{ something }}> you're creating a performance issue. Because { something } is always a new object. It automatically rerenders all the useContext(context) consumers whenever the provider is rendered. So, plz take a look at useMemo ;-)
There's a reason why no mature solutions use React context for stored values. They use it only to keep the store itself (that's the same object always). Because otherwise any change of the store will rerender all the children that use the context. I highly recommend you to take a look at useSelector code in react-redux. Or at any other similar solution. At now there's no simple way to avoid using own-implemented observable model, to make a performant solution. Context API is too simple to do it properly. But I hope soon we will seen something that solves the problem.
Thx, for the article. But there's 2 things you probably should to worry about (especially if you want to use it in production for big applications):
When you write code like
<Provider value={{ something }}>you're creating a performance issue. Because{ something }is always a new object. It automatically rerenders all theuseContext(context)consumers whenever the provider is rendered. So, plz take a look atuseMemo;-)There's a reason why no mature solutions use React context for stored values. They use it only to keep the store itself (that's the same object always). Because otherwise any change of the store will rerender all the children that use the context. I highly recommend you to take a look at
useSelectorcode in react-redux. Or at any other similar solution. At now there's no simple way to avoid using own-implemented observable model, to make a performant solution. Context API is too simple to do it properly. But I hope soon we will seen something that solves the problem.This. Context is fine for small isolated use cases, but any mid to large app is guaranteed to suffer performance issues.
Thank you, Stepan!
Ok, so there is an issue from a performance perspective.
That is what I didn't know.
Yeah,
useMemois good for optimizing performance 👍I will take a look at
useSelectorcode!