commit | 19dfb4b4fd70306133f4ac059e681d2ae2aeb64d | [log] [tgz] |
---|---|---|
author | Andres Olivares <[email protected]> | Thu Jan 21 18:02:03 2021 |
committer | Commit Bot <[email protected]> | Thu Jan 21 19:29:18 2021 |
tree | a6f510e322132b8da4e11f8371db05e88cf9b99b | |
parent | 83e37a7ccd50c6928fd50e72493d28666f249272 [diff] |
[module.json extensions] timeline views Bug: 1134103 Change-Id: I168d621048b93f00b16b6f7d4fd11d2e4bb4f031 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2631963 Commit-Queue: Andres Olivares <[email protected]> Reviewed-by: Tim van der Lippe <[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