February 11, 2026 at 3:57 AM
We did, check out: react.dev/reference/de...
The thing I'm adding is being able to show what the DevTools Profiler will show you when you run it, embedded in the docs themselves.
The thing I'm adding is being able to show what the DevTools Profiler will show you when you run it, embedded in the docs themselves.
React Performance tracks – React
The library for web and native user interfaces
react.dev
February 10, 2026 at 7:59 PM
We did, check out: react.dev/reference/de...
The thing I'm adding is being able to show what the DevTools Profiler will show you when you run it, embedded in the docs themselves.
The thing I'm adding is being able to show what the DevTools Profiler will show you when you run it, embedded in the docs themselves.
For tracking where updates came from, you can click the "update" in the tracks to see were the setState came from.
Here's an example: react.dev/reference/de...
Here's an example: react.dev/reference/de...
React Performance tracks – React
The library for web and native user interfaces
react.dev
February 10, 2026 at 7:58 PM
For tracking where updates came from, you can click the "update" in the tracks to see were the setState came from.
Here's an example: react.dev/reference/de...
Here's an example: react.dev/reference/de...
We show the component tree in the Components track. We'd like to make it easy to click to go to the Components tab for React DevTools, but that requires the browser to add link support.
February 10, 2026 at 7:58 PM
We show the component tree in the Components track. We'd like to make it easy to click to go to the Components tab for React DevTools, but that requires the browser to add link support.
Does this diagram help? It uses the React Performance Tracks to explain what React is doing, and what you'll see when you use the tracks:
github.com/reactjs/reac...
github.com/reactjs/reac...
February 10, 2026 at 6:11 PM
Does this diagram help? It uses the React Performance Tracks to explain what React is doing, and what you'll see when you use the tracks:
github.com/reactjs/reac...
github.com/reactjs/reac...
February 8, 2026 at 10:45 PM
Reposted by Ricky
useEffectEvent makes handling events in Effects much easier and saves unnecessary unmounting and remounting of listeners. It now has awesome new docs: react.dev/reference/re...
Thank you to @ricky.fm the updates, and @danabra.mov and @stephanjnoel.bsky.social for reviewing
Thank you to @ricky.fm the updates, and @danabra.mov and @stephanjnoel.bsky.social for reviewing
useEffectEvent – React
The library for web and native user interfaces
react.dev
February 6, 2026 at 3:44 PM
useEffectEvent makes handling events in Effects much easier and saves unnecessary unmounting and remounting of listeners. It now has awesome new docs: react.dev/reference/re...
Thank you to @ricky.fm the updates, and @danabra.mov and @stephanjnoel.bsky.social for reviewing
Thank you to @ricky.fm the updates, and @danabra.mov and @stephanjnoel.bsky.social for reviewing
Reposted by Ricky
Take me down to the Parallax city where the far moves slow and the near moves quickly
February 1, 2026 at 3:40 PM
Take me down to the Parallax city where the far moves slow and the near moves quickly
Why do you need to attach the listener in a ref callback? We flush effects sync in updates for user events exactly for this use case
January 31, 2026 at 3:42 PM
Why do you need to attach the listener in a ref callback? We flush effects sync in updates for user events exactly for this use case
There are two blockers to autodeps. 1) people really hate the idea of not seeing the array (but that’s fine, you could still choose to write it) and 2) if you think about useEffectEvent primarily as “untracked” then you need to see the deps. But if you think of it as separating events, you don’t
January 31, 2026 at 3:14 AM
There are two blockers to autodeps. 1) people really hate the idea of not seeing the array (but that’s fine, you could still choose to write it) and 2) if you think about useEffectEvent primarily as “untracked” then you need to see the deps. But if you think of it as separating events, you don’t
Yeah I love that. And that works with my other concern: how does this make sense with auto deps where you don’t write/see the dependency array.
January 31, 2026 at 3:10 AM
Yeah I love that. And that works with my other concern: how does this make sense with auto deps where you don’t write/see the dependency array.
My thought process is “i need to connect to a socket and subscribe to a connect event. I don’t want to resubscribe for that event, so let me move this to an effect event”
January 30, 2026 at 9:52 PM
My thought process is “i need to connect to a socket and subscribe to a connect event. I don’t want to resubscribe for that event, so let me move this to an effect event”
The problem is thinking from the components perspective (how props flow in) not the effects perspective (what values resubscribe).
The thought process should be the same with or without the dependency array.
The thought process should be the same with or without the dependency array.
January 30, 2026 at 9:51 PM
The problem is thinking from the components perspective (how props flow in) not the effects perspective (what values resubscribe).
The thought process should be the same with or without the dependency array.
The thought process should be the same with or without the dependency array.
Reposted by Ricky
@ricky.fm Thank you for updating react.dev/reference/re... page.
Also thanks to @danabra.mov, @aurorascharff.no @stephanjnoel.bsky.social, @brenelz.com for adding feedback
Also thanks to @danabra.mov, @aurorascharff.no @stephanjnoel.bsky.social, @brenelz.com for adding feedback
useOptimistic – React
The library for web and native user interfaces
react.dev
January 30, 2026 at 9:31 PM
@ricky.fm Thank you for updating react.dev/reference/re... page.
Also thanks to @danabra.mov, @aurorascharff.no @stephanjnoel.bsky.social, @brenelz.com for adding feedback
Also thanks to @danabra.mov, @aurorascharff.no @stephanjnoel.bsky.social, @brenelz.com for adding feedback
Maybe it's
"This lets you call this function from a Effect as an "event". Since it's an event, the Effect does not need to include it as a dependency. Please read Dan's learn docs about this, they're very good."
"This lets you call this function from a Effect as an "event". Since it's an event, the Effect does not need to include it as a dependency. Please read Dan's learn docs about this, they're very good."
January 30, 2026 at 7:19 PM
Maybe it's
"This lets you call this function from a Effect as an "event". Since it's an event, the Effect does not need to include it as a dependency. Please read Dan's learn docs about this, they're very good."
"This lets you call this function from a Effect as an "event". Since it's an event, the Effect does not need to include it as a dependency. Please read Dan's learn docs about this, they're very good."
yeah, i struggle with explaining it simply in the reference section tbh - i don't want to say something about reactivity, or removing deps because you should start from 'i need an event' not 'i need to fuck with deps'
January 30, 2026 at 7:17 PM
yeah, i struggle with explaining it simply in the reference section tbh - i don't want to say something about reactivity, or removing deps because you should start from 'i need an event' not 'i need to fuck with deps'
