commit | fa4cb93f41d40bac1321c9e7ed0860bb732cd592 | [log] [tgz] |
---|---|---|
author | Wolfgang Beyer <wolfi@chromium.org> | Mon Jun 17 11:38:21 2024 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 17 12:28:38 2024 |
tree | a8236420603ed6e6345d10235ac4293de3da2fc1 | |
parent | cd8ec631f436b6a860bc8fad7f0e201a8b90c5ec [diff] |
Remove console insights dogfood config After launching console insights to all supported countries, we no longer need a separate dogfood (finch) config. Corresponding Chrome CL: https://crrev.com/c/5620871 Bug: 346487159 Change-Id: I3e42674f6404872d88efd5b3066b9e91242c912a Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5618854 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Commit-Queue: Wolfgang Beyer <wolfi@chromium.org>
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: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools