[go: up one dir, main page]
Google Git
Sign in
chromium / devtools / devtools-frontend / a0e0f7163bd234a548f870f194caaf15c0ba7d8f
commita0e0f7163bd234a548f870f194caaf15c0ba7d8f[log] [tgz]
authorJack Franklin <jacktfranklin@chromium.org>Thu Nov 02 13:51:56 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Nov 02 14:15:14 2023
treefeb829a38545d9b880b75ed0457f2ceb92437bb2
parentf7b0797a6ea423e8d19fb841534b92273b4803b4 [diff]
RPP: show a download raw events button if the trace errors

In the event that the trace parsing fails, this means we have at least
gathered all the events. In that case, let's add a download button
because that will greatly aid in debugging, and allow users to report
bugs with traces even if the engine fails.

Bug: none
Change-Id: I9371b8ccf04558c2a5c34a0f2eb65da456e5c5e0
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5000426
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Andres Olivares <andoli@chromium.org>
Commit-Queue: Andres Olivares <andoli@chromium.org>
1 file changed
tree: feb829a38545d9b880b75ed0457f2ceb92437bb2
  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. build
  15. buildtools
  16. .clang-format
  17. .editorconfig
  18. .eslintignore
  19. .eslintrc.js
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .gn
  25. .mailmap
  26. .npmignore
  27. .npmrc
  28. .style.yapf
  29. .stylelintignore
  30. .stylelintrc.json
  31. AUTHORS
  32. BUILD.gn
  33. codereview.settings
  34. DEPS
  35. LICENSE
  36. OWNERS
  37. package-lock.json
  38. package.json
  39. PRESUBMIT.py
  40. README.md
  41. tsconfig.json
  42. 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 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