Forget the action hell in Redux! Just dispatch reducers by using Repatch.
The power of higher-order reducers
Enhance the functionality of your existing reducers by wrapping them with a higher-order reducer, like redux-undo's undoable, which adds undo/redo functionality.
React Redux Real World Examples 〜先人から学ぶReact Reduxの知恵〜
React Reduxを使ってプロダクトを作りはじめて、かれこれ半年くらい経ちます。 しかし、どうもうまく書けていない気がすることがときどきあり、悩んでいたところ、ツイッターで次のような助言をもらいました。
Unreal Scoop: Making a “Compiling Shaders…” Screen
Unreal has a reputation amoung the ill-informed for being plagued by shader compilation stutter. As an attribute of Unreal itself, this is basically made up – devs are just not always doing what they are supposed to do pre-ship to avoid this issue. I’ll elaborate, but basically, to avoid compiling shaders during gameplay, you want to do it up-front, like during an initial loading screen, which maybe says “Compiling shaders” on it, and not let the player begin until it’s done. To do that last part properly, you need a little bit of C++. I had to do this for InFlux Redux recently, so here’s mine.
GitHub - pmndrs/zustand: 🐻 Bear necessities for state management in React
🐻 Bear necessities for state management in React. Contribute to pmndrs/zustand development by creating an account on GitHub.
Performance & Request Waterfalls | TanStack Query React Docs
Application performance is a broad and complex area and while React Query can't make your APIs faster, there are still things to be mindful about in how you use React Query to ensure the best performa...
Memory Efficient RL | Unsloth Documentation
We're excited to introduce more efficient reinforcement learning (RL) in Unsloth with multiple algorithmic advancements:
Common Sense Refactoring of a Messy React Component | Alex Kondov
One thing I've learned from all the consulting I've done is that rewrites rarely lead to anything good. Almost in all cases, when you have an application runnin
Real-World React: Designing Frontend Architectures That Survive Production | Workshops | Faris Aziz
Most React workshops focus on building features. This one focuses on keeping them alive. In production, React applications fail in ways that local environments never show: partial outages, slow dependencies, silent errors, broken rollouts, and performance regressions that only appear under real traffic. This workshop is a practical, architecture-first walkthrough of how experienced teams design React systems that stay resilient, observable, and scalable long after the first release. We will explore how component architecture, reconciliation in practice, and runtime failure patterns shape performance and operability far more than memoization tricks or framework features. Using React and Next.js as shared reference points, we will work through concrete patterns for failure recovery, error containment, safe rollouts, and post-deployment confidence. This is a hands-on, experience-driven workshop based on real production constraints, tradeoffs, and lessons learned from operating large React applications at scale. Attendees will leave with a mental model for building frontend systems that can fail safely, recover quickly, and ship continuously without fear. Most of the workshop is framework and library-agnostic, but we'll use React and Next.js as our common ground for communication and examples. This is not an exhaustive masterclass; it's a conversation starter and experience share to jumpstart your journey toward battle-tested software architecture.
React 16.x Roadmap – React Blog
This blog site has been archived. Go to react.dev/blog to see the recent posts. You might have heard about features like “Hooks”, “Suspense”, and “Concurrent Rendering” in the previous blog posts and talks. In this post, we’ll look at how they fit together and the expected timeline for their availability in a stable release of React. An Update from August, 2019 You can find an update to this roadmap in the React 16.9 release blog post. tl;dr We plan to split the rollout of new React features…
@tanstack/react-query - npmx
Hooks for managing, caching and syncing asynchronous and remote data in React
