mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-03 10:31:10 +08:00
Andrés Olivares
763593787a
At the moment, we use the no-exclusive-tests plugin to ban exclusive tests in the test/ repo. This is problematic because the rule doesn't work for the mocha extensions we use in DevTools (like describeWithMockConnection, etc.), meaning that exclusive tests like [1] can slip through the lint check. This CL adds a new rule that prevents call statements with the shape statement.only in the test base to account for this. The rule is applied to files ending with _test.ts and the previous rule is removed. [1] https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3898961/23/test/unittests/front_end/panels/timeline/SourceMaps_test.ts#80 (line 80) Bug: none Change-Id: If0e6ac9810c80da067faa1f2158b8bd45f8417f8 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3963115 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Andres Olivares <andoli@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).