Tim van der Lippe
09519f3c00
The swarm bots use :devtools_frontend_resources to figure out which files to send to the bots. Even though we have specified the generated TypeScript files and included in the GRD file, if the file does not exist on the filesystem on the bots. Therefore, if we force add it to the dependencies, we can make sure that the file is forcefully added. This is not the proper longterm fix, as it should find all dependencies recursively in the GN hierarchy tree itself. However, since we are using `deps` rather than `public_deps` in our actions, that is a plausible explanation as to why the swarm bots are not finding the files. Once we are back on stable ground, we are going to test that hypothesis and prevent this issue from occurring again. TBR=aerotwist@chromium.org No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I0cb00db954389ec1fbc03a1990d7fd1712c1ac51 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2287522 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org>
Chrome DevTools frontend
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
Source code
The frontend is available on chromium.googlesource.com.
Design guidelines
Please be aware that DevTools follows additional development guidelines.
Issue triage
The issue triage guidelines can be found here.
Workflows
Instructions to set up, use, and maintain a DevTools frontend checkout can be found here.
Additional references
- DevTools documentation: devtools.chrome.com
- Debugging protocol docs and Chrome Debugging Protocol Viewer
- awesome-chrome-devtools: recommended tools and resources
- Contributing to DevTools: bit.ly/devtools-contribution-guide
- Contributing To Chrome DevTools Protocol: docs.google.com
- DevTools Design Review Guidelines: design_guidelines.md
Source mirrors
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.
Getting in touch
-
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