mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-13 01:54:52 +08:00
Paul Lewis
0cd45e3e49
This reverts commit 25a9b3bd7404d49e55772ffba046ed8df65ad14e. Reason for revert: Memory snapshots work again Original change's description: > Revert "[DevTools]: Moves common to ES modules" > > This reverts commit e064553334d4b0c925f0b1f0e2e0234be66b71be. > > Reason for revert: Memory tool fails to take heap snapshots with this > error: https://imgur.com/hzR9Eqw > > Original change's description: > > [DevTools]: Moves common to ES modules > > > > This CL converts the contents of the common/ folder over to ES modules > > from the current custom module system. It includes statements in each > > file that will pollute the global namespace, allowing the non-ESM code > > to continue working as before. > > > > Bug: 1006759 > > Change-Id: Ib591e49155000381f85999a5da6c467ad0160996 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816563 > > Reviewed-by: Yang Guo <yangguo@chromium.org> > > Commit-Queue: Paul Lewis <aerotwist@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#699728} > > > Change-Id: Ic0d526780451e8bb4de538f11c85859a3badfb0f > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 1006759 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825463 > Commit-Queue: Yang Guo <yangguo@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#699835} Bug: 1006759 Change-Id: I48c7e84262bb295e5830cac8a79a274226df046c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825420 Commit-Queue: Paul Lewis <aerotwist@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#699981} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 75a39ca7ac8dcfc6a830db07a5a389ca9ab27b1d
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.