Performance Tooling for cross-execution context PostMessaging This change provides support to render post message event data on the timeline tracks and creates association lines between post message event dispatch and handler events. [Design Doc](https://docs.google.com/document/d/14v-muPKa4ylStxY4qlDi7KFWGEZkad-9j5jo9-FTAf4/edit?usp=sharing) [Relevant chromium.src PR](https://chromium-review.googlesource.com/c/chromium/src/+/5022285) Bug: 1500360 Change-Id: I2b35977225e28e345d636b207a9e63b04af7a9d5 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5023450 Commit-Queue: Sylvester Elorm Coch <elormcoch@microsoft.com> 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 project 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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools