Eval: use the GCP bucket and store examples there This CL uses the newly created GCP bucket in two ways: 1. `gclient sync` will now fetch the contents of the bucket. 2. The `upload_to_gcp.ts` script will upload the latest contents of the directory to GCP, and will then update the `DEPs` file with the latest revision. It first generates a hash of all the files in the directory to ensure that we do not end up uploading a folder that is identical to the existing one. R=alexrudenko@chromium.org Bug: 436223818 Change-Id: I28641b7eee64945c78a5fbdb3378f3633fc6a0ea Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6862825 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Alex Rudenko <alexrudenko@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.