Timeline for FLEDGE: also include service main thread. This is needed for the recently-added network tracing, as fetches happen on the main thread, not the V8 thread, so the previous filter was too narrow. (In the Android case, the renderer main thread would already be included). Bug: 1335914 Change-Id: Ib4d137e5b11b0fdb9c39da5f007c07e97c489537 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3773764 Commit-Queue: Maks Orlovich <morlovich@chromium.org> Reviewed-by: Victor Porof <victorporof@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.
Please be aware that DevTools follows additional development guidelines.
The issue triage guidelines can be found in docs/triage_guidelines.md.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
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