i'm launching a small (big) thing tomorrow
i learned a lot from building react scan. in browser devtools need to be:
minimal (to install + use, aren't annoying)
high utility (within the hot path of the workflow)
my next small ship will play into these
We have one remaining known bug in notifications where keyboard input events are periodically reported much higher than they are in reality- we are working on a fix for that
If you noticed React Scan showed a lot of FPS drops, but you didn't feel any slowdown, that is fixed in react-scan@0.3.3
Every time HMR was triggered when the tab was not focused, our internal logic would incorrectly track that as an FPS drop
New in React Scan v0.3
- View who rendered a component inside the notifications visualization by expanding it
- Fixes a bug causing incorrect "whats changed" values to be reported when selecting a component
- Toolbar slowdown notification count is now cleared after you view them
- Fixes a bug that caused the toolbar to be blurry at times
Full release notes in thread ->
This update ships with the first version of react-scan integration. For now we only use it to visualize renders. When you enable "Outline Renders" option you'll start seeing the indicators of React renders on top of the app.
How do you actually fix slow renders after you know about them?
React Scan notifications tells you which props, state, and context caused a component to re-render
If you stop those from changing, and memoize the component, it wont re-render
If you're building a React app and haven't used React Scan (by @aidenybai): PLEASE DO.
Refactored the @avelinHQ codebase to prevent a plethora of unnecessary renders.
Much smoother now. 💪
🧵 Keep reading for specifics: