RPP: use "local metrics" and "field metrics" consistently This changes it because before we had "Live metrics" and "Field data" as the prominent terms, and that's a bit of a mixup. This CL makes us consistently use: - Local metrics - Field metrics Which is consistent; and avoids any confusion of "live metrics" which is not as clear as "Local metrics". To avoid confusion regarding the title of the view itself, we keep the title of the page to "Live metrics". So the way to think about this is: 1. We have a **Live metrics** page 2. That shows both **local metrics** and **field metrics** (if configured). (Thanks to @barrypollard for his input). R=paulirish@chromium.org Fixed: 404513461 Change-Id: Ief19e37ac4968d4fe47a6e58c40983dfeefd8986 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6624111 Reviewed-by: Paul Irish <paulirish@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@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.