Files
react-native-devtools-frontend/scripts
Simon Zünd 8247f33e14 [l10n] Remove 'removeUnusedEntries' test
The PRESUBMIT check using the code in question was removed in favor
of an ESLint rule. The tests have moved as well.

As these tests are not regularly run on CI, we didn't notice that the
test for localization utils broke. This CL fixes that.

R=wolfi@chromium.org

Bug: chromium:1180760
Change-Id: Iea3def7adcca7dc100931387e3978f9df29dfcfd
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2742486
Commit-Queue: Simon Zünd <szuend@chromium.org>
Commit-Queue: Wolfgang Beyer <wolfi@chromium.org>
Auto-Submit: Simon Zünd <szuend@chromium.org>
Reviewed-by: Wolfgang Beyer <wolfi@chromium.org>
2021-03-08 12:50:54 +00:00
..
2019-11-17 14:56:34 +00:00
2020-11-13 12:15:35 +00:00
2021-02-26 17:18:55 +00:00
2021-02-08 13:22:14 +00:00
2021-02-24 12:34:38 +00:00
2020-11-30 13:55:39 +00:00
2020-05-14 06:52:14 +00:00
2020-11-25 12:56:57 +00:00
2020-03-26 11:36:00 +00:00
2020-03-11 14:47:51 +00:00
2021-02-28 18:31:08 +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

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