React

Zustand is a minimal, but fun and effective state management library which just may improve your render performance.

A bit of a pivot from the Redwood gang, splitting RedwoodJS into Redwood GraphQL … To minimize disruption and provide clarity going forward, we’re renaming the existing RedwoodJS framework to Redwood GraphQL, reflecting its strength as a mature, stable framework built around GraphQL. … and the newfangled RedwoodSDK. Redwood has always been ultra opinionated (I […]

It’s not particularly obvious, but a child’s useEffect will run before a parent’s will. Let’s look at why.

I enjoyed this very straightforward, well-presented, useful article on how to create a keyboard shortcut hook in React from Tania Rascia. It’s part basic implementation, part designing an API pattern that feels right, part dealing with React hook eccentricities, and part dealing with edge cases. In the end, a pretty readable 86 lines of code.

“… props that match a property on the Custom Element instance will be assigned as properties, otherwise they will be assigned as attributes.”

Server-side component rendering can improve data loading efficiency over client-rendered SPAs. Despite their benefits, such as out-of-order streaming, they have limitations, including slow server action updates and lack of support for client-side interactivity. React Query complements RSC by managing client-side data updates, addressing some of RSC’s drawbacks.

JavaScript Rising Stars is interesting to look at year after year because of the simple methodology of measuring how many more GitHub Stars a project gets year after year. A project like React with a massive amount of star-based popularity isn’t guaranteed to top the list, and in fact this year clocks in at #7. […]

Million.js caught my eye a few months back because of the big claim it makes: Make React 70% faster. I ended up listening to a podcast with the creator, and the meat of it is: it removes the need for “diffing” the virtual DOM that React uses when re-rendering to find what needs to change, which […]

A nice bit of writing from Dan Abramov in which he argues for code that should run on the client, and then again for code that should run on the server. It feels like an elaborate setup to explain React Server Components in a part two. Is there some way we could split components between […]