mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-17 12:05:31 +08:00
Jack Franklin
0dda490e7c
This is the first in a long set of CLs that will begin to remove old engine functionality we do not need. I have started with the ThreadTracksSource enum and removed the BOTH_ENGINES flag; updating all the screenshot tests to use the new engine exclusively. In future CLs I will remove the enum and the flag entirely, but first I will go through and remove code that only runs for the OLD_ENGINE flag. Bug: 1499182 Change-Id: I7ab164e500576d044f334705d5e99649b3523e94 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5002389 Reviewed-by: Andres Olivares <andoli@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Andres Olivares <andoli@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).