commit | 6ed9f27a50b8247275fe2da632f06d68f5a02ec7 | [log] [tgz] |
---|---|---|
author | Tim van der Lippe <[email protected]> | Tue Feb 02 17:13:23 2021 |
committer | Commit Bot <[email protected]> | Tue Feb 02 21:08:29 2021 |
tree | e50b48ed712d58122bc3235034fc63b9b175ac93 | |
parent | 3a91cdb875dd8f45f7504e9e3910708a8bce3816 [diff] |
Generate HTML entrypoints in gen folder This makes sure we first generate the relevant files in the gen folder, before we perform the copy to the resources/inspector folder. [email protected] Bug: none Change-Id: Ic4b92358b4a46558512f3c5db4a0ebc1f708b5b5 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2666698 Auto-Submit: Tim van der Lippe <[email protected]> Commit-Queue: Paul Lewis <[email protected]> Reviewed-by: Paul Lewis <[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 in docs/triage_guidelines.md.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
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