commit | 3ec89ccf6b2e77a1b3a8600d86f5e79882f364fb | [log] [tgz] |
---|---|---|
author | Randolf <[email protected]> | Mon Jan 30 22:35:07 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 31 12:47:43 2023 |
tree | 960669c1211400096c794ecca87c7caa21bac42b | |
parent | 9762db476cd7414d3ce351f32a0564421f66901f [diff] |
Add @puppeteer/replay to test dependencies This PR adds @puppeteer/replay for dogfooding in replay E2E test. Bug: 1411188 Change-Id: I4c65fce494df70c01d862e99c5f355d578ae0bfa Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4206547 Commit-Queue: Randolf Jung <[email protected]> Reviewed-by: Simon Zünd <[email protected]>
The client-side of the Chrome DevTools, including all JS & 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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools