Hello,

I've just published React-Tracked v2.0.0 as well as use-context-selector v2.0.0. Remembering its history, React-Tracked is one of my major OSS products into which I have put much effort. Prior to it, I had developed a library called reactive-react-redux, which aimed to eliminate selectors for render optimization. React-Tracked was developed for React Context because, at that time, people sometimes overused Redux only for render optimization. use-context-selector is a selector-based solution, and React-Tracked on top of it is a selector-less solution. Time has passed, and React-Tracked now also supports Redux and Zustand in addition to React Context.

I had been wondering if I should continue maintaining React-Tracked, because for global state we have better options such as Zustand, Jotai, and Valtio. The last two offer a selector-less solution. I was about to declare the termination of React-Tracked when I noticed an improvement to make it compatible with useMemo, which is also required for Valtio. It's an improvement in a sense, but it can cause extra rerenders, so it's less optimization to enable memo compatibility.

Anyway, that made me decide to keep maintaining React-Tracked and release v2. I wonder if it will gain some traction or fade out. My concern is that some people may have already given up due to memo incompatibility in v1 and might not notice that v2 fixes it. What can I do about it?

Happy Hacking.

0 comments

HackDiary#080

HackDiary#079

HackDiary#078

HackDiary#076

HackDiary#075

See all posts from Daishi Kato