commit | 71ae782372f15d72ac41dc47250485a8b14d45aa | [log] [tgz] |
---|---|---|
author | Tim van der Lippe <[email protected]> | Wed Sep 02 14:33:31 2020 |
committer | Commit Bot <[email protected]> | Wed Sep 02 15:13:20 2020 |
tree | 111741138af5dfdde400ed24572ccf9a297b7f83 | |
parent | 207e2f9fdc5109d6c371b7ce2b9c8321c02c08eb [diff] |
Migrate media to devtools_entrypoint [email protected] Bug: 1101738 Change-Id: I670a299a808b9164fb76385efc37d87d5257336d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2390621 Commit-Queue: Tim van der Lippe <[email protected]> Reviewed-by: Jack Franklin <[email protected]>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Please be aware that DevTools follows additional development guidelines.
The issue triage guidelines can be found here.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found here.
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: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools