mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-27 16:35:54 +08:00
Ergun Erdogmus
6c326da0de
The part that takes a lot of time in running unit tests is actually spinning up the browser and connecting to it. `watch-unittests` command starts the file watcher for Karma test runner which runs the tests on file change. You can use this without `watch` script and by just rebuilding the target. When combined with `watch` command, this enables you to run unit tests instantly after a file change. Bug: none Change-Id: Icd71230b5b455254dc25b4cef5f6ae72c5dbba06 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5012787 Commit-Queue: Simon Zünd <szuend@chromium.org> Auto-Submit: Ergün Erdoğmuş <ergunsh@chromium.org> Reviewed-by: Simon Zünd <szuend@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).