[Extensions] Promisify chrome.devtools.network namespace Before this commit, methods in the chrome.devtools.network namespace and the Request object (specifically getHAR and getContent) were limited to callback-based interaction. After this commit, network.getHAR and Request.getContent are promisified. They return a Promise when called without a callback. Unit tests now cover these methods, ensuring they correctly handle responses from the ExtensionServer. This was accomplished by applying the promisification pattern to the network-related implementations in ExtensionAPI.ts and updating the associated declaration and test files. *Note* since I'm not a Typescript expert I used Gemini to help write this. Any feedback on a simpler or more readable solution is welcome. Bug: 496604552, 496604551, 496616808 Change-Id: I2be23a77aeefaf06e26b57dfe01490b0ab5c164c TAG=agy Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7802275 Auto-Submit: Justin Lulejian <jlulejian@chromium.org> Reviewed-by: Danil Somsikov <dsv@chromium.org> Commit-Queue: Danil Somsikov <dsv@chromium.org> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.