-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[No QA] Performance tracking with flipper-plugin-performance #4760
[No QA] Performance tracking with flipper-plugin-performance #4760
Conversation
Onyx captures a lot of measures. We can inspect those on the Flipper Timeline
Update the metro configuration so that when `CAPTURE_METRICS` is `true` we pass aliases to allow capturing data with the Profiler component Otherwise React would just skip capturing metrics in release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some notes on the changes
This comment has been minimized.
This comment has been minimized.
Onyx metrics add a lot of bars to the timeline this might be distracting, we might update the
|
Usages through `process.env` cover missing .env files
Ready for review Tested on all platforms
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great changes! PR is really awesome! Just had some comments/questions...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replied to the questions
Would push updates on Monday
7c0282e
to
9ea80ba
Compare
Addressed requested changes. Ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, @Luke9389 do you want to take a look at this?
|
Onyx hash updated. |
Hey, sorry. Getting caught up here. |
This is an awesome PR @kidroca Yea, we can flag this as [No QA] I think. |
@kidroca are you using flipper with the non-mobile platforms as well? It worked for me on your branch with iPhone, but I didn't get any devices recognized on Flipper for web. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I read through the review iterations to get familiar with some of these changes. Tested on my end and looks good.
Thanks @Luke9389 Flipper is for native platforms only :) can use Chrome Dev Tools for testing the website - just without as much fanciness. Some things are easier - other things less so. |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
Hi, I'm sorry to intervene, but I have an issue with web version not building:
I made sure my packages are up to date and I haven't done any changes to my .env or anything. Commenting out these 2 lines fixes the problem. I am not exactly sure if this is a missing package issue or that code is not meant to be run on web at all. Anyway, I am up-to-date on Thanks. |
So you've installed the new packages with The code is not supposed to run on web, but the bundler analyzes all Hi, I'm sorry to intervene, but I have an issue with web version not building:
|
I did another go on mac with The issue is related to this
Because of the above, webpack would follow imports to Adding App/config/webpack/webpack.common.js Lines 14 to 23 in 8a5cf2d
This would mean that some unused code gets bundled into the end bundle: It doesn't add much, but still I think the right thing to do is not to include unused modules |
This prevents an error related to bundling: Expensify#4760 (comment)
…per-plugin [No QA] Fix regression on web due to #4760
🚀 Deployed to production by @roryabraham in version: 1.0.88-2 🚀
|
This has been deployed to production and is now subject to a 7-day regression period. |
cc @marcaaron
Details
Adds the Flipper side of
react-native-performance
where we can see a timeline of our performance updatesIn order to see some data on the timeline I've integrated the
<Performance>
component similar to howit's used on the example project here: https://github.com/oblador/react-native-performance/blob/ccfe4557350a0ef206268e9a50317d9cc2480464/examples/vanilla/App.tsx#L28
Related Issues
$ #4656
$ #4549
$ Expensify/react-native-onyx#101 (package hash should be updated after the onyx PR is merged)
Tests
.env
configuration and setCAPTURE_METRICS
totrue
npm start -- --reset-cache
flipper-plugin-performance
QA Steps
N/A
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android