[cleanup] Remove our custom implementation of `lit/static-html`. When we were using `litTagName` heavily, we rolled our own custom implementation of `lit/static-html`, which was optimized for the common case in our codebase. With the removal of `litTagName` we are left with only one place in the codebase where we use, and in this particular code path our optimization is useless (and even costs us more), since the `litTagName` changes in every loop iteration. Use the upstream `lit/static-html` module instead and remove our custom logic. This makes all regular calls to `html` faster in DevTools, since we no longer preprocess the template string looking for potential static parts. Drive-by-fix: Fix the build for `front_end/third_party/lit`. Bug: 370734442 Change-Id: I9dc70ecab8bb224e926776ebc50c1f8189f21b0c Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6126880 Commit-Queue: Nikolay Vitkov <nvitkov@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@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.