mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-13 01:54:52 +08:00
Takuto Ikuta
7c57958680
This reverts commit0d4947c37e. Reason for revert: https://crbug.com/1211770 Original change's description: > Reland "use python3 in devtools-frontend by default" > > This reverts commita8336c1e58. > > Reason for revert: > use universal_newlines instead of text for > https://docs.python.org/3/library/subprocess.html#subprocess.Popen > > I tried to divide this CL in to make py2/3 compatible and switch in > another CL. But that hit another issue due to the difference of string > type around io.StringIO and cStringIO.StringIO like > https://logs.chromium.org/logs/devtools-frontend/buildbucket/cr-buildbucket.appspot.com/8846743161604002304/+/u/compile/raw_io.output_failure_summary_ > > So decided to re-land the switch with fix for known issue. > > I confirmed this works for python3.6 too. > > Original change's description: > > Revert "use python3 in devtools-frontend by default" > > > > This reverts commit37c0bf698d. > > > > Reason for revert: > > Compatibility issues with python 3.6. > > > > Original change's description: > > > use python3 in devtools-frontend by default > > > > > > Fixed: 1205624, 1205625 > > > Change-Id: Iddaf2a49bffd92140d1877784ffd9f5dd83ac3de > > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2902988 > > > Auto-Submit: Takuto Ikuta <tikuta@chromium.org> > > > Commit-Queue: Takuto Ikuta <tikuta@chromium.org> > > > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > > > Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org> > > > > Change-Id: Ic426154f58798dd8631f9bac101521f0b25ea54c > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2906060 > > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > > Bug: 1210939, 1205624, 1205625 > Change-Id: Ia7ddf5ab37c8df3e2f682bf89cb55ef30e663341 > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2909053 > Commit-Queue: Takuto Ikuta <tikuta@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> Bug: 1210939 Bug: 1205624 Bug: 1205625 Bug: 1211770 No-Tree-Checks: true No-Presubmit: true Change-Id: Ic3a6add15b4126dfe818b445a5227253d296ee96 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2910016 Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Michael Achenbach <machenbach@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
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).