[RC 0.1.2] - cleanup, improvements, Re-renders History, Components Tree and more

[pivanov]

Summary:

• fix: cleanup + biiome - 0 errors, 0 warnings
• feat: custom postcss plugin rem2px to prevent target page styles to brake ours
• feat: Re-renders History
• Components Tree
  • Search
  • Breadcrumb
  • Resizing + preserve dimentions
• improve: extension now work with new outlines
• improve: inspector UI animations and components
• improve: getOverrideMethods
  • chain updates through all renderers to ensure consistency across different React renderers (e.g., React DOM + React Native Web in the same app)
  • add overrideContext: using overrideProps internally to update the context provider's value prop

[vercel]

@pivanov is attempting to deploy a commit to the Million Team on Vercel.

A member of the Team first needs to authorize it.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/aidenybai/react-scan@195

commit: a06c31e

[RobPruzan]

@pivanov would you mind providing a summary of what this PR does in the description?

Both helpful for reviewing so I don't miss anything/makes sure I fully understand context, and is useful for historical records

Something that I think is helpful for large PR's is commenting clarifications on changes themselves in the PR to explain context. For example, some of these helpers are complex but idk their purpose immediately when reviewing, so quickly describing why they exist is very useful

[RobPruzan]

Here is a video of me using the timeline for the first time, it doesn't seem to work for context/state updates that the component is definitely subscribed to, so the UX will not be good unless the history is consistent

Its also not intuitive for me to use/seems to be some bugs in the state management (watch video). I'm not exactly sure how to use it, or how I'm supposed to use it to optimize/debug the app

And I think we need to make sure this is implemented as an auxiliary feature. The times you will need this is infrequent, so it shouldn't be the first thing you see in the inspector.

This also seems to replace that whats changed view (no longer pops up when state changes). That was well received, so we need to find a way to keep that as is and implement the state update timeline in a different location (note i do notice the what's changed view still exists when you go back in history, but point stands)

Screen-2025-01-22-173240.mp4

[pivanov]

It's not finished yet ... I'm still working on it.
I will let you know when it's ready for testing

[RobPruzan]

LGTM