Fix What's new item URLs and update from 149 to 150 This also removes the code backticks in the CSS at rules headline, as they don't render. Change-Id: I95cc92bdb61bd0907ffae7de3a2fa382afe351bd Bug: 527001183 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8025689 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Mathias Bynens <mathias@chromium.org> Commit-Queue: Matthias Rohmer <mrohmer@google.com> (cherry picked from commit 3d497f07a2ef9deda9bc5f99f298e88365b517d7) Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8034467 Auto-Submit: Matthias Rohmer <mrohmer@google.com> Commit-Queue: Mathias Bynens <mathias@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.