Google GitGoogle Git
Sign in
chromium/devtools/devtools-frontend/f2af58b5e89924ea8e8def5643c9c798db163748
commit
f2af58b5e89924ea8e8def5643c9c798db163748
[log]
author
Philip Pfaffe <pfaffe@chromium.org>
Wed Jul 05 11:34:31 2023
committer
Philip Pfaffe <pfaffe@chromium.org>
Mon Jul 17 10:38:00 2023
tree
3347b4c0297027712f09fdd1c68caf472494ccd2
parent
15667aaea13e9aedafb31551d0eb23ecc0f46e01 [diff]
Tidy up ExtensionServer helpers

- Eliminate second path to add extensions for tests: We can use the
  regular extension registration path in tests except for the iframe.
  Pull the iframe setup into a separate method that tests can stub away.
- Correctly reset the devtools API object between tests. With the switch
  to new headless we were always hitting the catch in cleanup().

Bug: 1451146
Change-Id: I2d23f15690d9e04afac8df9190e222cb442dc5a4
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4664805
Commit-Queue: Philip Pfaffe <pfaffe@chromium.org>
Reviewed-by: Danil Somsikov <dsv@chromium.org>
(cherry picked from commit a88e571bc5923241886ed68bb9a46a456b302f0e)
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4685557
2 files changed
tree: 3347b4c0297027712f09fdd1c68caf472494ccd2
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .mailmap
  22. .npmignore
  23. .npmrc
  24. .style.yapf
  25. .stylelintignore
  26. .stylelintrc.json
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. DEPS
  31. LICENSE
  32. OWNERS
  33. package-lock.json
  34. package.json
  35. PRESUBMIT.py
  36. README.md
  37. tsconfig.json
  38. 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