mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-13 01:54:52 +08:00
Eric Leese
5377e0bbb2
This makes several improvements to test output: - Screenshots are no longer printed to console or saved to an html file. This is unnecessary now that they are uploaded to rdb. - When a test is retried, the timeout hook was not correctly hooked, which produced unexpected errors from multiple done calls. This has been fixed. - Screenshot error message now includes causes, which displays the pending async stacks on timeout. - Driveby fix to improper assertion in console-helpers. Bug: None Change-Id: Ia76f88ad9fbf1236a47a1f27eff41ee93d1a28a5 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5349145 Commit-Queue: Eric Leese <leese@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@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).