commit | 74ea1ec215ddfe8657bcc1f0077cd0ac0f4f254d | [log] [tgz] |
---|---|---|
author | Jack Franklin <jacktfranklin@chromium.org> | Mon Mar 20 11:49:21 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 20 14:41:36 2023 |
tree | 04769caf69615614e3d28b26d883d69d33d0ddc3 | |
parent | 3287c528bddefec5b5ab37d53784de056e2ff014 [diff] |
Implement InteractionsTrackAppender Bug: 1421748 Change-Id: I6cced4df4b4995c5f6359dbd237cee76306e4309 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4341493 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Andres Olivares <andoli@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@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