[docs] Mention the ways to keep an eye on DevTools' development. This was previously in the Contribution Guide Google Doc, and is worth preserving. Bug: 354102605 Change-Id: I11a8466ef6869b51adf18bd09a94ee5c3cf7b55c Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5803107 Commit-Queue: Simon Zünd <[email protected]> Auto-Submit: Benedikt Meurer <[email protected]> Reviewed-by: Simon Zünd <[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 project 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:
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
Code reviews mailing list: [email protected]
All open DevTools tickets on crbug.com
Follow these Twitter accounts: @ChromeDevTools, @DevToolsCommits, @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, @bmeurer
Subscribe to [email protected] mailing list for all reviews of pending code
Watch developers.google.com/web/updates/ -or “What's new in DevTools” posts.
Follow Umar's Dev Tips: umaar.com/dev-tips/
Use Chrome Canary and poke around the experiments.