mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-30 18:03:48 +08:00
Tim van der Lippe
1009500fe4
This reverts commit696a03e075. Reason for revert: Chromium build performance issues should be mitigated. Original change's description: > Revert "Move rollup configuration to front_end/rollup.config.js" > > This reverts commit11c3e48f98. > > Reason for revert: Has a negative performance impact for Chromium builds > > Original change's description: > > Move rollup configuration to front_end/rollup.config.js > > > > This makes it easier to change the rollup configuration and allows > > us to introduce the terser minification plugin. > > > > R=jacktfranklin@chromium.org,aerotwist@chromium.org > > > > Bug: 1084578 > > Change-Id: Ie9c3447913a9d6ca59905267472a8bad328642b2 > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2208134 > > Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> > > Reviewed-by: Paul Lewis <aerotwist@chromium.org> > > Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> > > TBR=aerotwist@chromium.org,tvanderlippe@chromium.org,jacktfranklin@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 1084578 > Change-Id: If359d1398796330e8569a1ecf0af9d94ad08abae > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2218065 > Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org> > Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> # Windows presubmit is broken: crbug.com/1095581 No-Presubmit: true Bug: 1084578, 1095581 Change-Id: I4a96fc91bc5c6e1394535dd2c5e413ecadfdcf3d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2246509 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Simon Zünd <szuend@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
- jsdoc_validator - enforces the use of Closure type annotations
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).
Closure
DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the closure_runner (in ./closure) and jsdoc_validator custom jars using the python scripts in their respective directory.