mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-03 02:21:05 +08:00
Patrick Brosset
5d02bbd8c7
I use the standalone devtools-frontend checkout process like most people working on devtools, however I placed this repo inside chromium here: D:\dev\chromium\devtools\devtools-frontend This way I have both src and devtools-frontend side by side. I just realized that this prevented me from running the css linter. Indeed, run_lint_check_css.js tries to find the path to stylelint exe file based on whether devtools is standalone or integrated in chromium.src. If it sees a directory named chromium inside the path, it assumes devtools is integrated in chromium.src which, in my case, is wrong. The change attempts to make this logic a little bit more safe by checking a longer part of the path. This resolves my issue. Bug: 1198532 Change-Id: I872429da0751280bef5a4ec68602001421f55056 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2821855 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Brandon Walderman <brwalder@microsoft.com> Commit-Queue: Patrick Brosset <patrick.brosset@microsoft.com>
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
- optimize_svg_images.py - manually run when changing svg images
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).