commit | 79a7fc9c426881822e8ffc6033059035449c74ce | [log] [tgz] |
---|---|---|
author | Yang Guo <yangguo@chromium.org> | Mon May 23 13:48:26 2022 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 24 14:36:00 2022 |
tree | 6df5d152a1122399c65854a3f6344e258a920a4b | |
parent | e41bd1343a9fda359e72b0a467906687ee6f7fde [diff] |
Add string description for eval scope type Bug: 1328014 Change-Id: I9d0ea6044d1c520539bec2e5aec9eabfd7d042ee Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3660424 Auto-Submit: Yang Guo <yangguo@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org>
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: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools