ReactJS developers now face a new library called use-thunk that promises to streamline state handling by cutting through Redux’s complexity. The author, drawing on Dan Abramov’s original Redux design, argues that thunk functions can replace the traditional action/reducer split, while keeping useReducer and useContext as the only built‑in hooks.

Critics point out that Redux still forces developers to write a large switch statement inside a single reducer, making the function unwieldy. The need to dispatch every action feels redundant, and the single giant state object can lead to accidental cross‑updates, especially when slicing the store for modularity.

Similarly, useContext can mimic derived actions by passing state and setState, but it requires creating a new context each time and custom async helpers. The pattern is a workaround rather than a documented feature, leaving developers to juggle context placement and state updates manually.

The author’s ideal solution, showcased in the demo-use-thunk repo, separates UI rendering from global‑state management, uses a single thunk concept, and supplies default state per object. By eliminating explicit contexts and dispatch calls, the approach promises cleaner code and easier onboarding for teams accustomed to React Hooks.