mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-07 04:26:32 +08:00
This adds an additional_readme_paths.json file that specifies all directories of third_party packages that we include in the DevTools bundle. The file is used as part of Chromiums about:credits machinery to list all licenses of all third_party software (accessible via chrome://credits). It also updates the names of the packages to use the full name, which is used as header of the license. To ensure that this file remains up-to-date, we also include a GN action that verifies all third_party directories listed in our GRD are included in the .json file. Lastly, add the missing license for Puppeteer. R=yangguo@chromium.org Bug: 1282407 Change-Id: Ia3142ab5bbc79804c56bc754934b9aaf1d186d7f Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3386943 Commit-Queue: Tim Van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Yang Guo <yangguo@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).