mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-03 10:31:10 +08:00
Jack Franklin
98edce7f17
Once we've got the `yargsObject`, we pull out all the keys we want, which are all the configuration flags bar the special yargs keys `$0` and `_`. The bug here was that once we pulled out that configuration, we didn't update it, and instead kept referring to `yargsObject` in the rest of the code. This meant that when we dynamically set the `test-server-type` flag, we set it on `yargsObject`, but we needed to set it on the configuration flags object so that the settings propagate down into the test runner. Bug: chromium:1186163 Change-Id: Ia88bb25588651fac4c11783f551651d27ccd0334 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3075379 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Tim van der Lippe <tvanderlippe@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).