commit | d4f6802db692145c54fa73b37e35c4635ae6a8ef | [log] [tgz] |
---|---|---|
author | Tim van der Lippe <[email protected]> | Wed Dec 15 13:21:59 2021 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 15 14:51:00 2021 |
tree | f97df5200b186b82c02b463d53efde58784dced4 | |
parent | d692cac31ffea822377407e775750d9f6a042eba [diff] |
Migrate to private class members in panels/emulation/components/ [email protected] Bug: 1222126 Change-Id: I7ba8d899d519ca262ccca8a425b4c5a7a1d6ae51 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3341604 Reviewed-by: Simon Zünd <[email protected]> Commit-Queue: 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 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