I stopped destructuring everything

I stopped destructuring everything
4 minutes by Matt Smith

Matt explains why he stopped using JavaScript destructuring by default. While destructuring can make code shorter, it can also reduce clarity by hiding where values come from. Matt argues that keeping object names often makes code easier to read and maintain. He still uses destructuring in simple, local cases, but only when it improves readability rather than just reducing typing.

KendoReact vs. OSS: Know Before You Choose
sponsored by Progress Telerik

What do you actually get for free - and what ends up costing engineering time? A practical look at the tradeoffs between OSS and commercial React UI libraries.

How to handle custom invoker commands in React
4 minutes by Sergio Xalambrí

The Invoker Commands API lets buttons trigger actions on specific elements using standard or custom commands. Custom commands use a prefix and fire a native event on the target element instead of running built-in behavior. Since React lacks an onCommand prop, you attach a listener via a callback ref and return a cleanup function to remove it on unmount. This keeps DOM wiring simple while leaving application logic in separate functions.

React router v8 makes middleware a baseline
7 minutes by Roman Fedytskyi

React Router v8 makes middleware a default part of the stack rather than an optional experiment. This lets teams centralize auth checks, logging, headers, and redirects in one place instead of scattering them across components and server adapters. The route hierarchy now acts as a policy tree, not just a rendering tree. Teams with auth logic in components and redirect rules spread across loaders have a cleaner path to consolidating that debt.

React compiler
17 minutes by Neciu Dan

React Compiler is a build tool that automatically adds memoization to your components at compile time, so you no longer need useMemo, useCallback, or React.memo in your source code. It analyzes data flow to track dependencies accurately and caches values using simple array checks rather than hooks. The compiler works with React 17, 18, and 19, and skips any component it cannot safely optimize rather than risk breaking it. Real production results show meaningful gains, including faster interactions and lower render times across large codebases.

React testing questions that trip up engineers
17 minutes by How To Test Front End

The post explains common React testing mistakes that often appear in frontend interviews. It covers how to avoid weak tests, why implementation details should not be tested, when to use mocks, fake timers, and act(), and how to test features like debounced inputs, drag-and-drop, and browser APIs. The goal is to help developers write reliable, maintainable tests and prepare for React testing interview questions.

And the most popular article from the last issue was:

• Reverse engineering ChatGPT web interface