mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-03 02:21:05 +08:00
Benedikt Meurer
7b31ea2848
Prior to this change, the generated CSS files would show up un "no domain" in DevTools-on-DevTools, rather than in the correct paths (next to the source code). This is because we inject the CSS via `<style>` tags (or in some cases still adopt them to the shadow root), and put a relative path into the `sourceURL` annotation. DevTools-on-DevTools is not able to reconstruct the proper URL in these cases, because it doesn't know the contextual base URL. With this change, we use `import.meta` to construct the proper URL at the time when importing the `.css.js` file, and stick that into the `sourceURL` annotation. Bug: 391381439 Change-Id: Ia965faa19d5119a2f70f840cf20d8d5b914856d7 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6221305 Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
DevTools Scripts
Development workflow scripts
These are scripts that can be useful to run independently as you're working on Chrome DevTools front-end.
The newer scripts such as for testing and hosted mode are written in Node.js, which has become the standard toolchain for web apps. The older scripts such as building (e.g. bundling and minifying) are written in Python, which has first-class support in Chromium's infrastructure.
Overview
Folders
- build - Python package for generating DevTools debug and release mode
- chrome_debug_launcher - automagically finds Chrome Canary and launches it with debugging flags (e.g. remote debugging port)
- closure - see section on Closure Compiler below
- gulp - experimental build process written in node.js & gulp to remove the dependency on Chromium-specific build tools (i.e. gn and ninja)
- hosted_mode - run DevTools on a localhost development server
Python Scripts
- compile_frontend.py - runs closure compiler to do static type analysis
- Note: the compiled outputs are not actually used to run DevTools
- lint_javascript.py - run eslint
Node.js scripts
The easiest way to run the node.js scripts is to use npm run which displays all the commands. For more information on the specific npm run commands, take a look at the primary devtools front-end readme (../readme.md).