commit | 61cb47a73c921c2be190843e75960861c11c1bac | [log] [tgz] |
---|---|---|
author | Connor Clark <cjamcl@chromium.org> | Thu Mar 06 01:22:14 2025 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 06 01:52:09 2025 |
tree | b62a895a04953be0ad6ed07987570c2b14cbcd0d | |
parent | 1460ded4b6c32b1578774fd60c488f7aaeabd437 [diff] |
[RPP] Fix bug where script contents are exported in trace These events were not properly being filtered out of non-enhanced traces. Bug: 394373632 Fixed: 401087758 Change-Id: I8ab5bf83ae4dd42a9520933f22008702cc6e85a9 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6330595 Auto-Submit: Connor Clark <cjamcl@chromium.org> Commit-Queue: Paul Irish <paulirish@chromium.org> Reviewed-by: Paul Irish <paulirish@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.