Files
react-native-devtools-frontend/scripts
Simon Zünd ae9845e539 [scripts] Add new 'rename-legacy-global.mjs' migration utility
This CL is a temporary migration helper for the *-legacy.ts removal
effort. It's a slightly better search&replace that also adds the
necessary import statement if needed.

R=jacktfranklin@chromium.org

Bug: 1442410
Change-Id: Idcba121da6176f745db3e98d9e9ba0ac836d7b7b
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4774939
Commit-Queue: Simon Zünd <szuend@chromium.org>
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
2023-08-14 11:18:52 +00:00
..
2023-08-09 10:26:55 +00:00
2020-11-13 12:15:35 +00:00
2021-05-04 11:10:07 +00:00
2021-06-10 10:09:30 +00:00
2020-03-26 11:36:00 +00:00
2020-03-11 14:47:51 +00:00
2022-05-12 11:08:38 +02: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

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).