[RPP] Track async scheduler for async JS calls The AsyncCallStacksHandler now tracks the JS call that scheduled a particular JS function. Basically, this adds the opposite direction of the relationships we were tracking: before we had scheduler -> schedulee this CL tracks schedulee -> scheduler. This is done with the twist that instead of starting from a JS entry point trace event (e.g. FunctionCall, EvaluateScript, etc.) we start from the profile calls themselves. This will be useful in reconstructing the full (async) callstack of a given JS call in its details, which will be done in a follow up Bug: 381392952 Change-Id: I4a3983e2cc21f8c3ccf3c856fade99ed845f3421 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6059857 Commit-Queue: Andres Olivares <andoli@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@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.