Million.js (@milliondotjs) 's Twitter Profile
Million.js

@milliondotjs

creators of react-scan.com, Million Lint (yc w24) • Discord: million.dev/chat

ID: 1644643765930594304

linkhttps://million.dev calendar_today08-04-2023 10:10:59

521 Tweet

9,9K Followers

6 Following

Aiden Bai (@aidenybai) 's Twitter Profile Photo

we're starting a React Scan working group: if you: 1. use react scan daily 2. want to try early releases & give feedback send me a dm :)

we're starting a React Scan working group:

if you: 
1. use react scan daily 
2. want to try early releases & give feedback

send me a dm :)
kian bazza (@kianbazza) 's Twitter Profile Photo

If you're building a React app and haven't used React Scan (by Aiden Bai): PLEASE DO. Refactored the Avelin codebase to prevent a plethora of unnecessary renders. Much smoother now. 💪 🧵 Keep reading for specifics:

Million.js (@milliondotjs) 's Twitter Profile Photo

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

Krzysztof Magiera (@kzzzf) 's Twitter Profile Photo

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.

Million.js (@milliondotjs) 's Twitter Profile Photo

Can't figure out why a component is re-rendering? React Scan can tell you exactly what caused the re-render after selecting it