Google Git
Sign in
chromium / devtools / devtools-frontend / 9e176519afd505a405a50d9312c926ef97003ec3
commit9e176519afd505a405a50d9312c926ef97003ec3[log] [tgz]
authorConnor Clark <cjamcl@chromium.org>Thu May 15 22:05:12 2025
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 15 22:38:22 2025
tree9012b712719fdf786927f928b717f16556751723
parentc972280f13a077ca7d6d13fe1a3d6973e0a09fdd [diff]
Convert scriptId from enhanced trace to string

The SDK model expects this to be a string, but the trace actually had
numbers for these fields. This prevented the Performance panel's
SourceMapsResolver from updating the names of things in stack frames.

Bug: 40899278
Change-Id: I87436f80e11a1f8cd99fc22df7c21451d796d7ab
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6551981
Reviewed-by: Paul Irish <paulirish@chromium.org>
Commit-Queue: Paul Irish <paulirish@chromium.org>
Auto-Submit: Connor Clark <cjamcl@chromium.org>
2 files changed
tree: 9012b712719fdf786927f928b717f16556751723
  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: