mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-07 04:26:32 +08:00
This is to make const enum in protocol.d.ts works with esbuild in unittest. Without this, const enum usage from protocol.d.ts is not replaced with esbuild. So I need to make protocol.d.ts actual TypeScript file and make it has corresponding JavaScript file with defined enums. I also need to tweak how protocol.js is imported to make build/test pass in both tsc and esbuild with child CL. Bug: 1278663 DISABLE_THIRD_PARTY_CHECK=change generated/ and importing files Change-Id: Ic5f27633c85bbfe8647636beef9b8625f33eabdd Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3367593 Reviewed-by: Tim Van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@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
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).