commit | 937f463144810330d5bb4b30a0cb2a68ff34e9cb | [log] [tgz] |
---|---|---|
author | Nikolay Vitkov <nvitkov@chromium.org> | Fri Jan 03 14:02:02 2025 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 03 17:42:50 2025 |
tree | 3bc5d9fd1e972a3087d6baaaf1ba5ee4bfabb511 | |
parent | ef6162477b01a92907e72ae08e1f8f6824523a99 [diff] |
Revert "[eslint] Prefer TypeScript `interface` over type aliases." This reverts commit af6c6337aab54aabe5976c43379f4444b03e3106. Reason for revert: The latest version of EsLint v9 does not work with the plugin added here, also the rule does more that just change shape objects from type to interface. Original change's description: > [eslint] Prefer TypeScript `interface` over type aliases. > > We have a mix of `type` and `interface` usage throughout our codebase, > that is sometimes difficult to follow and reason about. We should follow > the suggestion from the TypeScript PM and use `interface` consistently > where possible. This leads to better type display in errors and makes > our codebase easier to read (b/c consistency). > > This CL adds the `etc/prefer-interface` ESLint rule to accomplish this. > > Fixed: 387237537 > Change-Id: Idd6775094ba94b8397f626191788437f6b156dc6 > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6135001 > Commit-Queue: Nikolay Vitkov <nvitkov@chromium.org> > Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org> > Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Bug: 387237537 Change-Id: I6ecf18bfdaa4ad9efb17f0801def528035f9e703 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6140555 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Auto-Submit: Nikolay Vitkov <nvitkov@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.