Files
react-native-devtools-frontend/scripts
Tim van der Lippe 3e704e9618 Add Dispatcher base-interface to enforce type-safety
To make sure that typescriptified dispatchers use the object
notation, we have to signal to the InspectorBackend that
we use the object notation. As such, add a base interface
with an interface method called `usesObjectNotation` to make
sure that all dispatcher implementations use this method.

A follow-up CL will make the required changes to the
InspectorBackend to call the dispatcher with the correct
method arguments.

R=jacktfranklin@chromium.org,aerotwist@chromium.org
CC=sigurds@chromium.org,janscheffler@chromium.org

Bug: 1081686
Change-Id: I1fa9338afa44d26cc63dce84b9d88a936c4f35e4
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2207236
Reviewed-by: Paul Lewis <aerotwist@chromium.org>
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
2020-05-19 10:02:16 +00:00
..
2020-05-18 12:48:46 +00:00
2019-11-17 14:56:34 +00:00
2020-03-19 14:32:47 +00:00
2020-03-19 10:51:02 +00:00
2020-03-12 14:53:52 +00:00
2020-03-26 16:58:20 +00:00
2019-06-10 23:19:12 +00:00
2020-05-14 06:52:14 +00:00
2020-03-26 11:36:00 +00:00
2020-03-11 14:47:51 +00:00

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.