commit | d723dbaf1086737a432aeaaccdabefa70fea4c58 | [log] [tgz] |
---|---|---|
author | Alex Rudenko <alexrudenko@chromium.org> | Tue Apr 29 08:35:58 2025 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 30 07:38:14 2025 |
tree | 15b22f2085d2db0cc710f842f18f9b9b3e4cd0ce | |
parent | 08eb38a20b5c15fd5241c84b2174dd29e244cae0 [diff] |
Migrate presubmit to v2 - migrated to the presubmit version 2 - removes tests from running on presubmit - removes the rdb wrapper (test results without a wrapper http://screen/6a3kPXZ9sEyhcPo.png) - improves messaging to only report if something is wrong or if there is an error using canned checks as an example. Details log of execution can be retrieved via `git cl presubmit -v -v`. - extended format to non-js files Docs: https://www.chromium.org/developers/how-tos/depottools/presubmit-scripts/ Bug: 414511913 Change-Id: I0686989dceb67b7026fd08a3cb7a987965c54b2e Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6490749 Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Auto-Submit: Alex Rudenko <alexrudenko@chromium.org> Reviewed-by: 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.