mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-05 19:41:12 +08:00
Tim van der Lippe
1b5567f78a
To remove the module.json file in perf_ui, we need to migrate the resources to the new `generate_css` template. However, perf_ui is a bit special, in that it doesn't properly use the widget structure. As such, it sometimes injects CSS in places where there is no clear shadowRoot available. Therefore, it is not possible to migrate to CSSStyleSheet in combination with adoptedStylesheets. As a workaround (to unblock the module.json removal), we augment `generate_css` to add legacy file generation. All remaining resources in DevTools will migrate to these `.css.legacy.js` files. That's because these resources either are special (perf_ui) or are used in the `device_mode_emulation_frame` which can't use `CSSStyleSheet` itself. The files export an object, rather than a plain string. That's because we need to be able to distinguish what string is referencing a CSS file path and which strings contain the actual CSS styles. By using an object, we can remain using the `typeof` check for string in the legacy CSS infrastructure and otherwise destructure the object. After this, we can remove perf_ui from the module.json structure and properly bundle+minify the CSS resources. R=jacktfranklin@chromium.org Bug: 1190991, 1127902 Change-Id: I7523333e8025ae5fe5ed74b99b4e45907ff9ad97 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3275787 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>