Roll browser-protocol and CfT Manual rebaseline of memory.test.ts due to the changes introduced by https://crrev.com/c/7653807. This roll requires a manual review. See http://go/reviewed-rolls for guidance. Rolling CfT pin toghether with browser-protocol files: https://chromium.googlesource.com/chromium/src/+log/ce01102937348db7b88c8a4257ee4b3ac702eb1a..04ac77e14165e21ccff4c87567968d1a86187a18 In case of failures or errors, reach out to someone from config/owner/COMMON_OWNERS. Roll created at https://cr-buildbucket.appspot.com/build/8687479648037263889 R=chrome-devtools-waterfall-gardener-emea-oncall@google.com Bug: none Change-Id: I170dfb3b4158186bd4827427c3b6c26758cc08da Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7662889 Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Owners-Override: Simon Zünd <szuend@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.