| commit | d38bb9f317c07bd20a6ea8c5bbc30f43809c3000 | [log] [tgz] |
|---|---|---|
| author | Nikolay Vitkov <[email protected]> | Tue Apr 22 17:21:37 2025 |
| committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 23 07:11:21 2025 |
| tree | d98e83a702c241122c9baffaa1381d060c3d42b1 | |
| parent | b55c964ae04c19fa1260f0499bbac9107f5bb056 [diff] |
Update EsLint to newer version Needed to allow the bug to be fixed and closed. Bug: 402358297 Change-Id: I1e3c6008b6da565cbfc59c021bc4f67ba5b6a6f0 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6479834 Reviewed-by: Benedikt Meurer <[email protected]> Commit-Queue: Benedikt Meurer <[email protected]> Auto-Submit: Nikolay Vitkov <[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.