commit | b50d50e5fc0b5ea6a61b5a949999ceaa57cca9e9 | [log] [tgz] |
---|---|---|
author | Adam Raine <[email protected]> | Thu Oct 12 17:42:50 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 17 17:35:02 2023 |
tree | b0a8330b2be3eb07eebd14189c8b0e516b58acd5 | |
parent | 884cb45cd38b19e3e1fb9cf7edf970b7d21f13ed [diff] |
[Lighthouse] Add category metric compatibility Should have been added in: https://crrev.com/c/4863112 Bug: None Change-Id: Id4cf0a3fa55170a07936d3ee08f08e41882b28c6 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4935921 Reviewed-by: Mathias Bynens <[email protected]> Commit-Queue: Adam Raine <[email protected]>
The client-side of the Chrome DevTools, including all TypeScript & 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: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools