commit | ebc0d8f20c0e47440e8774dba7ccaed307be56f9 | [log] [tgz] |
---|---|---|
author | Wolfgang Beyer <wolfi@chromium.org> | Fri Mar 17 16:04:24 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 20 15:12:51 2023 |
tree | 9d370968c17e2c0514eca625e2d557949abcc87b | |
parent | 74ea1ec215ddfe8657bcc1f0077cd0ac0f4f254d [diff] |
[UMA] Metrics for adding a new header as an override Bug: 1383097 Change-Id: I5177aaff6f41066b0d2e6b1290092324d4ae722c Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4350316 Reviewed-by: Danil Somsikov <dsv@chromium.org> Commit-Queue: Wolfgang Beyer <wolfi@chromium.org>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
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.
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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools