commit | 93cdac74cf715e16b263a6781be4b4ee045972d0 | [log] [tgz] |
---|---|---|
author | Adam Raine <asraine@google.com> | Mon Jul 31 16:54:33 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 31 18:06:32 2023 |
tree | 856a24495c42de8676134272c63318adfa836876 | |
parent | 5a4ecdbe35959550672c60ecae5f35a615eea632 [diff] |
[Lighthouse] Throw if the page handle is null It is possible for the page handle to be null. Lighthouse will still throw an error but it does not reference the actual problem: https://github.com/GoogleChrome/lighthouse/issues/15300 Bug: None Change-Id: I98f6834db600c2e2009fd542c7a910476151ef95 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4734731 Commit-Queue: Paul Irish <paulirish@chromium.org> Reviewed-by: Paul Irish <paulirish@chromium.org>
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: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools