[browser_tests] Rethrow in setupLegacyFilesForTest

This is part of a 3-way change to get rid of DOMMessageQueue in
LoadLegacyFilesInFrontend [1].

"ExecJS" can await promises, so all we need is to make sure that the
async function promise is rejected when the imports fail. Once this
CL has landed we can remove the DOMMessageQueue and just call
"ExecJS" with the default "await promise" option.

The last step is to remove the try-catch alltogether in the frontend.

[1]: https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/devtools/devtools_browsertest.cc;l=221-231;drc=f633fa3cf093bc8b9eb3243e7b05ff0d64e4bff9

R=alexrudenko@chromium.org

Bug: 382003727
Change-Id: I7cee60082f285cf3fe0ea562424269da74f5b989
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6063120
Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
Auto-Submit: Simon Zünd <szuend@chromium.org>
Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
Commit-Queue: Simon Zünd <szuend@chromium.org>
1 file changed
tree: 5241b32490e3cc2db7f5264f261c47671593c4c6
  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. .gitallowed
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .gn
  24. .mailmap
  25. .npmignore
  26. .npmrc
  27. .style.yapf
  28. .stylelintignore
  29. .stylelintrc.json
  30. AUTHORS
  31. BUILD.gn
  32. codereview.settings
  33. CONTRIBUTING.md
  34. DEPS
  35. favicon.ico
  36. LICENSE
  37. OWNERS
  38. package-lock.json
  39. package.json
  40. PRESUBMIT.py
  41. README.md
  42. tsconfig.json
  43. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

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

Source code and documentation

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.

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

There are a few options to keep an eye on the latest and greatest of DevTools development: