AIv2: Generalize node path resolution tool Rename and generalize the ResolveLighthousePath tool to ResolveDevtoolsNodePath to reflect that resolving a comma-separated path of node indices/tags to a backend node ID is a general DevTools capability rather than being exclusive to Lighthouse. Additionally, add i18n titles and accessibility reveal labels to the accessibility details tool's DOM tree widget payload, and integrate the isOriginAllowed context security helper across styling and accessibility tools for consistent origin lock enforcement. Bug: 510206549 Change-Id: Ibf71ef7971243bc85d080dadb6c754420b1246a1 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8004510 Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@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.