commit | 39884c04ddbe3d51e4891cb1948073d44dadb5f5 | [log] [tgz] |
---|---|---|
author | Adam Raine <asraine@chromium.org> | Wed Dec 04 22:24:55 2024 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 05 16:55:15 2024 |
tree | ebcce0c79540802d75de1724200731a51788f378 | |
parent | e46ebf29d8b0d4172c45595a1cfb87b26ff52582 [diff] |
[RPP] Add insight messages to related insight chips This adds image specific recommendations for the image delivery insight. In a future patch, these messages will move next to the image as designed in the mocks. For now the insight chips area will be fine. https://screenshot.googleplex.com/9gw3N97GuEz8rLh Bug: 372897377 Change-Id: Ifccb7b4c4f26f779f05cf3130c323ce22601064d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6065232 Commit-Queue: Adam Raine <asraine@chromium.org> Reviewed-by: Connor Clark <cjamcl@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 Chromium DevTools 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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.