//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
ProfileReplies
Loading...
I'm going on tour with the Next.js team in June! Coming to Amsterdam and London to share what's new in Next.js 16.3, hang out with the community, and answer your questions. • June 9: San Francisco: luma.com/vercel-408x • June 11: Amsterdam: luma.com/34nqdfc3 • June 18: London: luma.com/lfr946sc
That information would you use from the component tree for a specific timeline entry? Do you need the whole tree or just the parent/owner stack?
There are two ways to resolve the cognitive dissonance of being on Twitter while also caring about all the awful shit happening because of Twitter 1. Leave Twitter 2. Stop caring Profoundly disappointing how many people I like seem to have chosen the latter
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...