commit | 0d4dbaeca95bf627fed9b82596fc1ad9cfd205e0 | [log] [tgz] |
---|---|---|
author | Benedikt Meurer <[email protected]> | Wed Oct 23 13:21:11 2024 |
committer | Benedikt Meurer <[email protected]> | Wed Oct 23 14:10:30 2024 |
tree | 1833a56e6a1d4e7ad0235788c12b95da60851063 | |
parent | 9b1acc7a74c8f23e9b144002b887eb850645543e [diff] |
[lint] Read `lit-analyzer` options from toplevel `tsconfig.json`. This way the config is in a central place and can be reused for ts-lit-plugin. Bug: 375149136 Change-Id: Ic3805b059b5c9b0d103a152e1ff36b3c9c5245b6 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5953717 Auto-Submit: Benedikt Meurer <[email protected]> Reviewed-by: Danil Somsikov <[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.