mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-30 01:07:01 +08:00
Tim van der Lippe
63a4d3dcd6
This is a reland of b3373919f86df10c190a8672ca828c7ea4b920e5 Original change's description: > Convert ui/ARIAUtils.js to an ES module > > ES modules allow files to explicitly import and export symbols [1]. > This patch migrates ARIAUtils.js to an ES module, while maintaining > backwards compatibility with existing usages of `window.UI.ARIAUtils`. > > The build system is updated to copy these modules verbatim, as it no > longer require pre-processing to be loaded. The `module.json` no longer > includes this file as a script, to make sure it is not double-bundled > into `shell.js`. Instead, it is added to the new field `modules`, which > contains all modules. By doing so, it becomes clear which files are > converted to modules already and which require the legacy references > to the global scope. > > This module and future modules will be imported from `root.js`, which is > added to all existing HTML application files. > > Design Doc: https://docs.google.com/document/d/1h9dOy3nNPNfZ2AtZXzB-DwJqG4Oo37WWvKLCuzCcPzo/edit?usp=sharing > > [1]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import > > TBR=jochen@chromium.org > > Change-Id: Ie79c8f2fce3aff96fa28af0b575eae39bfe8e1a5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1748949 > Reviewed-by: Jochen Eisinger <jochen@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Commit-Queue: Tim van der Lippe <tvanderlippe@google.com> > Cr-Commit-Position: refs/heads/master@{#697238} Change-Id: I7544cbf4364d0b1a3c2f137a4d17a1afdb1d4aed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1810534 Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Tim Van der Lippe <tvanderlippe@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#697626} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: ec810baced8e07ca3e9f2b801703be433807d2a2
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
- local_node - installs a local runtime of node.js
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.