[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]>
1 file changed
tree: 084268c1e44c5415176c550d48b27a6cd011927a
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. extensions/
  7. front_end/
  8. inspector_overlay/
  9. node_modules/
  10. scripts/
  11. test/
  12. third_party/
  13. v8/
  14. .clang-format
  15. .editorconfig
  16. .eslintignore
  17. .eslintrc.js
  18. .git-blame-ignore-revs
  19. .gitattributes
  20. .gitignore
  21. .gitmodules
  22. .gn
  23. .mailmap
  24. .npmignore
  25. .npmrc
  26. .style.yapf
  27. .stylelintignore
  28. .stylelintrc.json
  29. AUTHORS
  30. BUILD.gn
  31. codereview.settings
  32. DEPS
  33. LICENSE
  34. OWNERS
  35. package-lock.json
  36. package.json
  37. PRESUBMIT.py
  38. README.md
  39. tsconfig.json
  40. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

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.

Additional references

Source mirrors

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.

Getting in touch