This reverts commit862107080d. Reason for revert: Chromium build issue fixed. Original change's description: > Revert "Reland "Remove support for remote modules"" > > This reverts commitb3859e8d65. > > Reason for revert: Breaking roll (https://ci.chromium.org/p/chromium/builders/ci/win-archive-rel/17700) > > Original change's description: > > Reland "Remove support for remote modules" > > > > This reverts commitd5044ddf05. > > > > Reason for revert: Fixed Chromium debug issue. > > > > Original change's description: > > > Revert "Remove support for remote modules" > > > > > > This reverts commit419c91eff6. > > > > > > Reason for revert: Breaks roll https://chromium-review.googlesource.com/c/chromium/src/+/2416805 > > > > > > Original change's description: > > > > Remove support for remote modules > > > > > > > > LightHouse is currently broken in Canary, because of problems with > > > > the appspot server. This isn't the first occurrence of this problem > > > > and it becomes increasingly more difficult to figure out why the > > > > server keeps on breaking. This is combined with a large infrastructure > > > > cost of supporting remote modules and a confusing debugging experience > > > > when working with it locally. > > > > > > > > The reason we had remote modules was the fact that these modules are > > > > too large to be included in the Chromium bundle. In the last months, > > > > we have made numerous remote modules bundled, by applying minifications > > > > and optimizations to each module. > > > > > > > > The remaining remote module that we are currently shipping is LightHouse. > > > > Since the remote appspot server is broken and unlikely to be fixed > > > > anytime soon, now is the best time to finally resolve the remote > > > > modules question. > > > > > > > > Therefore, we remove support for remote modules from the `module.json` > > > > files and `Runtime.js`. Additionally, we update the build system > > > > to properly generate the required files and load them via ES modules. > > > > > > > > We will be able to perform subsequent cleanups in the Runtime to remove > > > > more infrastructure related to scripts/remote modules, but given that > > > > this CL is already quite large we are doing that in a follow-up CL. > > > > > > > > Follow-up action items for the LightHouse folks are to further decrease > > > > the bundle size for LightHouse. Since we are now loading it via ES > > > > modules, we can now use ES imports in the `devtools-dt-bundle.js` as > > > > well. This allows us to remove the copy of the SDK files, as well as > > > > make use of proper ES exports, rather than the browserified requires. > > > > > > > > R=aerotwist@chromium.org,yangguo@chromium.org,paulirish@chromium.org > > > > > > > > Fixed: 1128890 > > > > Change-Id: Ib4271a8064b18d31b75d9e28dbe5e3cb3c77d7ff > > > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2416511 > > > > Reviewed-by: Paul Lewis <aerotwist@chromium.org> > > > > Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> > > > > > > TBR=yangguo@chromium.org,paulirish@chromium.org,aerotwist@chromium.org,tvanderlippe@chromium.org > > > > > > Change-Id: I9d3da08108a35d7dadeefd526ea9dbd562ad3432 > > > No-Presubmit: true > > > No-Tree-Checks: true > > > No-Try: true > > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2416519 > > > Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> > > > Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> > > > > Change-Id: I26bf0565297c8e167039362b30109d7020bbca56 > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2418431 > > Commit-Queue: Paul Lewis <aerotwist@chromium.org> > > Reviewed-by: Paul Lewis <aerotwist@chromium.org> > > TBR=yangguo@chromium.org,paulirish@chromium.org,aerotwist@chromium.org,tvanderlippe@chromium.org,alexrudenko@chromium.org > > Change-Id: I0ed24d32c9b68bc4cb8026f6fc362540800beeb0 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2418408 > Reviewed-by: Paul Lewis <aerotwist@chromium.org> > Commit-Queue: Paul Lewis <aerotwist@chromium.org> Change-Id: I8718e9d94c384a13fd18261f8f497d32418658fb Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2421690 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Paul Lewis <aerotwist@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