Al Muthanna Athamina 3ca07b9609 Disable assertion for debugger lanuage plugins test
Disable after resume assertion in the "can access wasm data directly"
test until we can find a way to remove flakiness by making the stopid
deterministic. Also include TODO and bug.

Bug: 1419802
Change-Id: I807e223cd44d08e560bc9c3f9bb21af934c0b116
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4771028
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
Commit-Queue: Almothana Athamneh <almuthanna@chromium.org>
2023-08-11 11:01:00 +00:00
2022-05-30 08:50:17 +00:00
2023-08-11 04:57:18 +00:00
2023-08-11 06:00:29 +00:00
2023-07-12 07:46:22 +00:00
2023-07-31 07:05:32 +00:00
2023-01-31 10:21:47 +00:00
2023-08-02 18:46:31 +00:00
2021-04-16 07:38:35 +00:00
2020-08-21 05:51:47 +00:00
2020-05-29 14:29:42 +00:00
2023-07-31 12:30:05 +00:00
2022-01-17 12:49:00 +00:00
2023-08-11 04:57:18 +00:00
2023-08-02 17:39:15 +00:00
2023-02-06 09:56:07 +00:00

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

Additional references

Source mirrors

DevTools frontend repository is mirrored on GitHub.

DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.

The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.

Getting in touch

S
Description
No description provided
Readme BSD-3-Clause
1.1 GiB
Languages
TypeScript 88.2%
JavaScript 5.7%
CSS 3%
HTML 1.4%
Python 0.8%
Other 0.8%