React: ESLint v10 Support & DevTools Bug Fixes

Transcript

Hey there, React developers! Welcome back to your daily dose of React goodness. I'm your host, and wow, what a Valentine's Day gift we have from the React team today - February 14th, 2026 is bringing us some sweet updates that are going to make our developer lives just a little bit easier.

Let's dive right into the main event - ESLint v10 support has officially landed in the React hooks plugin! This is one of those updates that might not seem flashy, but trust me, it's going to save you from those annoying peer dependency warnings that have been popping up since ESLint v10 dropped last week.

Azat S. really went above and beyond here, and I love the thoroughness of this contribution. They didn't just bump a version number and call it a day. We're talking about proper end-to-end testing with a complete ESLint v10 fixture, TypeScript config files, and comprehensive testing to make sure everything plays nicely together. The fact that all 5,082 tests passed? Chef's kiss! That's the kind of attention to detail that makes the React ecosystem so reliable.

What I find really encouraging about this PR is how it shows the React team staying current with the broader JavaScript tooling ecosystem. ESLint v10 brought some breaking changes - they removed the legacy eslintrc config and deprecated some context methods - but because the React hooks plugin already supported flat config since version 7, this transition was smooth as butter. It's like when you've been future-proofing your code and it finally pays off.

Now, let's talk about our second merged PR from Ruslan Lesiutin. This one's a DevTools fix that's all about those tricky edge cases that can drive you absolutely bonkers when debugging. The issue was in how Suspense components handle their children in the DevTools store. Before this fix, when the code tried to remove a child node, it would sometimes just remove the last item in the list instead of the actual node it was looking for. Imagine trying to find a specific book on your shelf and accidentally grabbing the wrong one - not ideal when you're trying to debug your app!

This is exactly the kind of fix that makes me appreciate good debugging tools even more. Ruslan added a simple but crucial check to make sure the child node actually exists in the parent's children list before trying to remove it. Seven lines of code, but those seven lines probably just saved countless developers from pulling their hair out over mysterious DevTools behavior.

You know what I love about today's updates? They're both perfect examples of maintainer love. One contributor is keeping us current with the latest tooling, while another is squashing those subtle bugs that can make debugging feel like detective work. Both changes might seem small, but they're the foundation that lets us focus on building amazing user experiences instead of fighting our tools.

For today's focus, here's what I want you to think about: if you're using ESLint v10 in your React projects, you can now update your React hooks plugin without any warnings. Take a few minutes to check your package.json and see if you can clean up any version conflicts. And if you've been experiencing any weird behavior in React DevTools with Suspense components, this fix might just solve those mysterious issues you've been seeing.

The React ecosystem keeps getting more polished, more reliable, and more developer-friendly with every single contribution like these. Whether it's staying current with ESLint or fixing edge cases in DevTools, every improvement builds on the last.

That's a wrap for today's episode! Keep building awesome things, and remember - even the smallest fixes and updates are moving the entire ecosystem forward. I'll catch you tomorrow with whatever new React goodness comes our way. Until then, happy coding!