mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-30 01:07:01 +08:00
Kriti Sapra
8733f78d00
`registerRequiredCSS`. There are two main edge cases: multiple calls to `this.registerRequiredCSS` and calls to properties of the object, e.g. `this._widget.registerRequiredCSS`. I have added cases to the ESLint rule to migrate these automatically. In ESLint tests, the output is produced after only a single pass of the rule. Keeping this in mind, the tests for multiple calls have been broken down into multiple tests cases. Bug: 1106746 Change-Id: If5a4827ec7230508c9208c6d23882499495be12a Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3053744 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Kriti Sapra <kritisapra@google.com>
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).