commit | 99c387484bd5efdb979844339a86586a73afb3da | [log] [tgz] |
---|---|---|
author | Ergun Erdogmus <[email protected]> | Fri Jun 16 08:40:17 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 19 09:22:53 2023 |
tree | 6787477ebc7817a81b98655b76e3bfaaeee0c9b5 | |
parent | 73dcbe434f81c62fa4883aac16ae8270dff58c5a [diff] |
Track badge activations in Elements panel Bug: 1455339 Change-Id: Ida4986e859276c2c332129e042b6bc9b96cefd37 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4614960 Commit-Queue: Ergün Erdoğmuş <[email protected]> Auto-Submit: Ergün Erdoğmuş <[email protected]> Reviewed-by: Benedikt Meurer <[email protected]>
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: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools