commit | 5fe6376f92f7a7c3d4085f0c13693adbbf062ce5 | [log] [tgz] |
---|---|---|
author | Jack Franklin <jacktfranklin@chromium.org> | Tue Feb 28 15:59:40 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 28 17:49:02 2023 |
tree | d1aeda7be31efe031c67780748522e035a192223 | |
parent | d5dc91ec5f7e0c408784cac6ec696547eed1529b [diff] |
Remove reset call to trace engine worker We are not running the new trace engine currently and therefore do not need to make this call. Bug: none Change-Id: I75f3ed4c65152d2f9d66d09217570258c5555596 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4295183 Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Andres Olivares <andoli@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Andres Olivares <andoli@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