mirror of https://github.com/react/react-native-devtools-frontend.git synced 2026-10-02 18:11:04 +08:00

Files

T

Nikolay Vitkov 58be9b4c44 [cleanup] Don't declare default in constructor (#1 )

This moves some of the default from the constructor
to the declaration methods, this requires less space and
also point easier to what is coming from outside and what
the constructor is doing.

Bug: 397260638
Change-Id: I67a00b28e2cc92394e4bceca431b3d6f662a7537
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6377983
Commit-Queue: Nikolay Vitkov <nvitkov@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>

2025-03-25 07:25:21 -07:00

e2e

[cxx_debugging] Shot-in-the-dark attempt to reduce flakiness

2025-03-14 02:25:36 -07:00

lib

C++ debugging extension: support type externref

2024-05-28 07:30:44 +00:00

src

[cleanup] Don't declare default in constructor (#1 )

2025-03-25 07:25:21 -07:00

tests

Update node_module dependecies

2025-03-12 06:49:46 -07:00

third_party

Updating license IDs to be spdx compliant

2025-02-25 01:23:45 -08:00

tools

[cxx debugging] Don't build stage 1 with autoninja

2025-02-17 04:50:08 -08:00

CMakeLists.txt

Upstream the C++ debugging extension

2023-08-02 17:41:02 +00:00

README.md

[cxx_debugging] Document e2e tests

2024-07-24 11:49:40 +00:00

tsconfig.json

[cxx_debugging] Allow umd access to fix build with new ts

2024-07-15 10:18:17 +00:00

README.md

Chrome DevTools C/C++ Debugging Extension

This extension enables debugging capabilities in DevTools for C++ programs compiled to WebAssembly.

Build the extension

Note: Currently, the extension supports only Linux builds.

Some of the extension's dependencies are not checked out by default together with devtools-frontend. To enable the dependencies:

Set the checkout_cxx_debugging_extension_deps flag to True in your .gclient config. For example:

solutions = [
 {
   "name"        : "devtools-frontend",
   "url"         : "https://chromium.googlesource.com/devtools/devtools-frontend",
   "deps_file"   : "DEPS",
   "managed"     : True,
   "custom_deps" : {
   },
   "custom_vars": {
     "checkout_cxx_debugging_extension_deps": True
   },
 }
]

Make sure to update the dependencies. Run:
```
gclient sync
```
Run the extension's two-stage build from the same directory:
```
./tools/bootstrap.py -debug ../../out
```

This creates two output directories in the out folder:

DevTools_CXX_Debugging.stage1 that contains some native binaries required for the second build stage.
DevTools_CXX_Debugging.stage2 that contains the built extension.

To get an overview of all available build options, run ./tools/bootstrap.py -help.

Run the extension

You can load the extension to Chrome directly from the DevTools repository root with the following command:

third_party/chrome/chrome-linux/chrome --load-extension=$PWD/out/DevTools_CXX_Debugging.stage2/src

Unittests

The extension contains TypeScript and general front-end components, which are tested via karma-based tests located in the tests/ folder. They follow the foo_test.ts naming convention used in DevTools front-end.

These tests are automatically run by default by tools/bootstrap.py unless you pass the -no-check argument there.

To explicitly execute them, run the ninja check-extension in the stage2 output directory.

E2e tests

There are e2e tests, found in the e2e/ directory, which test the entire flow, from compiling a project with debug symbols to running it in chrome and debugging it with devtools with the extension.

Running the e2e tests requires a special build which includes also building devtools-frontend and compiling the test projects with emscripten. To do that, use:

./e2e/runner.py run --build-root ../../out/e2e --v -C

The -C argument is only necessary on the first run in order to fully compile everything once. Subsequently it can be left out to run a little bit faster.