commit | 1e4e83c0ed431133c5cf077a1d9bf6e9505a6335 | [log] [tgz] |
---|---|---|
author | Tim van der Lippe <[email protected]> | Tue Oct 12 16:16:58 2021 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 13 06:45:11 2021 |
tree | 172b204c8571c3f5ad02ebc8ba20c7cac3d1fc17 | |
parent | 72b3cd4bcfe19cab83f6b3c46802f9289f6bde4f [diff] |
Migrate to private class fields in panels/css_overview [email protected] Bug: 1222126 Change-Id: I5e4ef796c80be2fc9c044b320efa6c6f1a37a135 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3219239 Auto-Submit: Tim van der Lippe <[email protected]> Commit-Queue: Simon Zünd <[email protected]> Reviewed-by: Simon Zünd <[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