commit | 5c694b455dc2a8c9d703398204e2d86e190ae7df | [log] [tgz] |
---|---|---|
author | Nikolay Vitkov <[email protected]> | Wed Jul 16 14:32:41 2025 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 17 04:48:52 2025 |
tree | ee7af6a7d86e5a139288120fcaeba0d00723f6f0 | |
parent | 4a80fb1be1b2a5c115d78494d4972bd4a325ced1 [diff] |
Move Memory test to E2E non hosted Fixed: 416405547 Change-Id: I7d84ed6a64f4c3a2d2c1bed1c96d1b7134f61bb1 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6759939 Auto-Submit: Nikolay Vitkov <[email protected]> Reviewed-by: Simon Zünd <[email protected]> Commit-Queue: Simon Zünd <[email protected]>
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/[email protected] 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.