[WebVitals] Do not store interaction target nodes This is a manual modification of the web-vitals.js library to prevent it from retaining DOM nodes. In some cases the DOM node may be removed before DevTools can make a reference for it, but that is preferable to keeping the node in memory when the user does not expect it. Bug: 376777343 Change-Id: I507273c93a4bbe5f2f5111e1a17e179efc583ef4 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6159204 Commit-Queue: Adam Raine <[email protected]> Reviewed-by: Connor Clark <[email protected]>
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/[email protected] 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.