mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-03 02:21:05 +08:00
Tim van der Lippe
30103efb6b
All relevant build output files are now put into gen/front_end. To make sure that we don't run into duplicate JS entrypoint files, we have to turn of the emit of these targets in front_end/BUILD.gn, such that build_release_applications can put its output there. Since build_release_applications takes the files from the front_end source directory, not the gen directory, this causes no issues. After this change, it is possible to use --custom-devtools-frontend with gen/front_end rather than resources/inspector. DISABLE_THIRD_PARTY_CHECK=Update TypeScript noemit R=aerotwist@chromium.org Bug: 1174013 Change-Id: Iad331ff0a28871a0ec297483fa03fbb485d05fb4 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2672031 Reviewed-by: Paul Lewis <aerotwist@chromium.org> Commit-Queue: 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
- 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).