mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-30 09:54:02 +08:00
When source code is in nested folders, the es_modules_import rule would incorrectly compute the containing folders from `front_end`. Thus, if you would have two sibling folders in `front_end/panels`, the rule would incorrectly determine that they are in the same folder, while technically they are in a different folder. Therefore, the logic is rewritten to compute the common prefix of the two paths. If either one path ends up resolving to just a file, we assume that they were both part of the same folder. In other words: iff after removing the common prefix you still are importing both paths across a folder boundary, they are considered a different folder. R=jacktfranklin@chromium.org Bug: 1187573 Change-Id: Ib34583e258e005a124735e17e6a92e829eb37ef3 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2773054 Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@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
- 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).