[source-map] Restructure 'scopes' proposal decoding

This CL prepares 'SourceMapScopesInfo' and 'SourceMap' to support
index source map support for the 'scopes' proposal.

We split the existing 'SourceMapScopesInfo.parseFromMap' function into
'decodeScopes' and a dedicated test helper. 'SourceMapScopesInfo' no
longer parses anything, but instead just receives already decoded
scopes and ranges.

We also add two methods so OriginalScopes and GeneratedRanges can
be added to an existing SourceMapScopesInfo after the fact. We'll
make use of these two methods for multiple things:

  1) Accumulate all the scopes info in an index source map into a
     single SourceMapScopesInfo object

  2) Convert bloomberg pasta function ranges into OriginalScopes
     and add them to a SourceMap's SourceMapScopesInfo.

  3) Allow an extension API to incrementally add OriginalScope
     trees to a SourceMap's SourceMapScopesInfo.

R=kimanh@chromium.org

Bug: 390337576
Change-Id: Ifb911f4daded05f58a470cfed8759cf44e86425b
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6185441
Commit-Queue: Simon Zünd <szuend@chromium.org>
Reviewed-by: Kim-Anh Tran <kimanh@chromium.org>
4 files changed
tree: a9437b1fea10450f58bc87eea678e6e998de1c59
  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. .clang-format
  15. .editorconfig
  16. .git-blame-ignore-revs
  17. .gitallowed
  18. .gitattributes
  19. .gitignore
  20. .gitmodules
  21. .gn
  22. .mailmap
  23. .npmignore
  24. .npmrc
  25. .style.yapf
  26. .stylelintignore
  27. .stylelintrc.json
  28. AUTHORS
  29. BUILD.gn
  30. codereview.settings
  31. CONTRIBUTING.md
  32. DEPS
  33. eslint.config.mjs
  34. favicon.ico
  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 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: