Type the visibleView check in ProfilesPanel.searchableView searchableView() tests whether the currently visible view has a searchableView() method of its own, which was done through an any cast with a no-explicit-any disable. Declare the shape it is probing for, with the method optional, and cast to that instead. The check stays a truthiness test on the property rather than a typeof check, so a view carrying a non-callable searchableView still behaves as before. Not every profile view has one: HeapProfileView and HeapSnapshotView do, the launcher view does not, which is why the probe exists. No behavior change. Bug: 40166562 Change-Id: Icdde08a919ac6231cc3f0ed080b13ffe090d97db Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8513498 Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Wolfgang Beyer <wolfi@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.