commit | e46ebf29d8b0d4172c45595a1cfb87b26ff52582 | [log] [tgz] |
---|---|---|
author | Andrés Olivares <andoli@chromium.org> | Thu Dec 05 14:43:37 2024 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 05 15:23:59 2024 |
tree | 6e4fe86577728093c8d493d372687c09bfe709ed | |
parent | 97238e1b91af789118f408106fbc4ce751bee445 [diff] |
[RPP] Introduce StackTraceForEvent helper It extracts the full call stack (including async calls) of a given event (at the moment only JS calls / ProfileCalls). We will use this to helper to display the call stack of a given event in its details. In the future support for extension entries will be added to it. Bug: 381392952 Change-Id: I1410b2ed0f85bb8f9e4799ae7b0606bbc7f247f5 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6074770 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Andres Olivares <andoli@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.