mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-05 11:31:31 +08:00
In release mode, the devtools_entrypoint prebundle step was missing the deps. We ran into this issue when we were moving the emulation panel into panels/emulation, which required some updates to the toolbox.ts entrypoint (crrev.com/c/2782540). The missing deps then required the rootdir logic to be changed, such that deps are correctly resolved relative to the gen-directory, not the source directory. This CL might improve build performance in release builds, since we are now properly using incremental references for our entrypoints and saving a bit of compilation time. DISABLE_THIRD_PARTY_CHECK=TypeScript fix R=aerotwist@chromium.org Bug: 1187573 Change-Id: I4662ac90ba50116cb668dfe3164fe725b74f9a37 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2782554 Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> 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).