Google Git
Sign in
chromium/devtools/devtools-frontend/6ca4ad9f4aac1de91c8b5095b8fdb558ad9e7c5e
commit
6ca4ad9f4aac1de91c8b5095b8fdb558ad9e7c5e
[log]
author
Connor Clark <cjamcl@chromium.org>
Tue Feb 25 18:14:23 2025
committer
Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri Feb 28 22:14:59 2025
tree
2201c573a830a7ddf0529bda5a75de4f9cd628b1
parent
317b92f637f38f83d49c68d0ec37c0deb3005404 [diff]
[RPP] Save source maps to trace metadata for enhanced traces

Also modify source map fetching in RPP to 1) never do it for non-fresh
traces and 2) ensure that the raw source map is always available for
purposes of saving to trace metadata (required a hack in SourceMap to
not unconditionally drop the raw payload).

Bug: 394373632
Change-Id: Icff6d0da8d66111e19ba9fd966c6ab5ab014262e
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6287830
Reviewed-by: Paul Irish <paulirish@chromium.org>
Commit-Queue: Connor Clark <cjamcl@chromium.org>
Auto-Submit: Connor Clark <cjamcl@chromium.org>
6 files changed
tree: 2201c573a830a7ddf0529bda5a75de4f9cd628b1
  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. .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. eslint.config.mjs
  36. favicon.ico
  37. LICENSE
  38. OWNERS
  39. package-lock.json
  40. package.json
  41. PRESUBMIT.py
  42. README.md
  43. tsconfig.json
  44. 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: