[RPP] Recommened which throttling settings to use * Network: recommened the closest preset based on CruX data. If no feild data, recommened nothing * CPU: always recommend 4x (for now) The Network portion currently is not implemented for the toolbar dropdown, as it requires some refactor to how CruX data is managed to query it outside LiveMetricsView. Bug: 311438203 Change-Id: I027de20bbda94c84dcd9084a26a1d9e724f17705 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6039744 Reviewed-by: Adam Raine <asraine@chromium.org> Commit-Queue: 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.