commit | 5111ff483c1e4e585a4e9d91f23928a209484d4b | [log] [tgz] |
---|---|---|
author | Simon Zünd <[email protected]> | Wed Aug 23 08:46:17 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 23 09:55:25 2023 |
tree | 084268c1e44c5415176c550d48b27a6cd011927a | |
parent | a24bca2a8822fa44df0ef95fdd24425b28976aa5 [diff] |
[legcay] Use 'common.js' instead of 'common-legacy.js' in Tests.js Instead of importing 'common-legacy.js' and using the self.Common global, we import 'common.js' directly and stash the module in a local variable. Note that we can't use static imports as 'Tests.js' is loaded as a classic script and loading 'Tests.js' as an ES module requires non-trivial code changes in Chromium. [email protected] Bug: 1442410 Change-Id: Ia5b47f2baae12ad7e1baf4a5bb8d2a34cabe3800 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4803867 Commit-Queue: Simon Zünd <[email protected]> Reviewed-by: Alex Rudenko <[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