mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-01 09:47:56 +08:00
Connor Clark
2bc3be29be
This reverts commit0651468562. Reason for revert: Cause of failure has been remedied. See: https://chromium-review.googlesource.com/c/chromium/src/+/2055398 Original change's description: > Revert "[Lighthouse] Rename Audits panel to Lighthouse" > > This reverts commit2ae53ef04d. > > Reason for revert: This CL breaks CI: https://ci.chromium.org/p/devtools-frontend/builders/ci/DevTools%20Linux/453. It looks like the layout test expects audits not lighthouse in the name, so it's probably in need of a 3-way merge. > > Original change's description: > > [Lighthouse] Rename Audits panel to Lighthouse > > > > Change-Id: Ia2ab175d2a3b6c8ded73aff8ff0f5582f5a8fa0c > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2044605 > > Commit-Queue: Connor Clark <cjamcl@chromium.org> > > Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org> > > Reviewed-by: Paul Irish <paulirish@chromium.org> > > TBR=paulirish@chromium.org,aerotwist@chromium.org,tvanderlippe@chromium.org,cjamcl@chromium.org > > Change-Id: Ia6d5f42a0e6ece4352696c51bf0de5754774cb0a > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2051983 > Reviewed-by: Paul Lewis <aerotwist@chromium.org> > Commit-Queue: Paul Lewis <aerotwist@chromium.org> TBR=paulirish@chromium.org,aerotwist@chromium.org,tvanderlippe@chromium.org,cjamcl@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1052111 Change-Id: I638ca9bd5cd94e02fb7318f2a7d7c66fca40e6c8 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2056866 Reviewed-by: Connor Clark <cjamcl@chromium.org> Reviewed-by: Paul Irish <paulirish@chromium.org> Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Connor Clark <cjamcl@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.