mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-03 02:21:05 +08:00
Tim van der Lippe
647e33b2a1
This reverts commitcc75dee3ba. Reason for revert: Race-condition fixed in devtools-compatibility.js Original change's description: > Revert "Implement lazy loading of modules" > > This reverts commit7c08ccfd54. > > Reason for revert: > > Breaks browser_tests. Steps to reproduce: > - Build Chromium's browser_tests target > - Run `xvfb-run -s "-screen 0 1024x768x24" out/Default/browser_tests --gtest_filter=DevToolsExtensionTest.TestDevToolsExtensionAPI` > - Observe this failure: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8897915672067501312/+/steps/browser_tests__with_patch_/0/logs/Deterministic_failure:_DevToolsExtensionTest.TestDevToolsExtensionAPI__status_FAILURE_/0 > > Original change's description: > > Implement lazy loading of modules > > > > Any module that is not autostart and has `modules` specified in its `module.json` > > will now have its entrypoint dynamically imported. Update the release build script > > to output the `modules` array as well so that the Runtime can load it. > > > > Add additional entrypoints to `platform` and `dom_extension` to be consistent > > with the naming patterns of all other modules > > > > Bug:1006759 > > Change-Id: If6d10a13a62354079e3f8ee49bee4ecdcffa6758 > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1893085 > > Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> > > Reviewed-by: Paul Lewis <aerotwist@chromium.org> > > TBR=yangguo@chromium.org,aerotwist@chromium.org,tvanderlippe@chromium.org > > Change-Id: I22e8a341e841a99df0df9808a419cc070dd81bea > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 1006759 > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1893087 > Reviewed-by: Yang Guo <yangguo@chromium.org> > Commit-Queue: Yang Guo <yangguo@chromium.org> TBR=yangguo@chromium.org,aerotwist@chromium.org,tvanderlippe@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1006759 Change-Id: Id69542e883fc4b852a79e83373773de256976f83 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1897686 Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Yang Guo <yangguo@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.