Google GitGoogle Git
Sign in
chromium/devtools/devtools-frontend/56d58c95494a6b90f3e79133895bdc8e8a79e6d2
commit
56d58c95494a6b90f3e79133895bdc8e8a79e6d2
[log]
author
Nancy Li <nancyly@chromium.org>
Wed Jun 18 10:59:52 2025
committer
Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri Jun 20 10:36:52 2025
tree
c878bcbdb7e0c1ce71c8e602894b73f1a63a5c97
parent
9824c8b1d0189af46b94e9092a31a21110ca61f6 [diff]
[RPP cpuprofile] Clean up the unnecessary code for cpuprofile

Originally I was looking the bug of removing JSRoot, then I find out all the three 'fake' trace event we injected, only partial of each are used, and no overlap, so I just tried to merge all to the 'real' synthetic cpuprofile one.

During the merging, i just update some string to enum member and also update the type check when export file by the way.

Bug: 341234884
Change-Id: If2ce79fc0312e427d392cf39b52bfc1ff5e2bbdb
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6652271
Reviewed-by: Paul Irish <paulirish@chromium.org>
Commit-Queue: Nancy Li <nancyly@chromium.org>
8 files changed
tree: c878bcbdb7e0c1ce71c8e602894b73f1a63a5c97
  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. .clang-format-ignore
  18. .editorconfig
  19. .git-blame-ignore-revs
  20. .gitallowed
  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. CONTRIBUTING.md
  35. DEPS
  36. DIR_METADATA
  37. eslint.config.mjs
  38. favicon.ico
  39. LICENSE
  40. OWNERS
  41. package-lock.json
  42. package.json
  43. PRESUBMIT.py
  44. README.md
  45. 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: