[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 117f1e5e922a407a69d47de2ce8635eaf1eb99da
commit117f1e5e922a407a69d47de2ce8635eaf1eb99da[log] [tgz]
authorJack Franklin <jacktfranklin@chromium.org>Mon Feb 27 16:21:45 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Feb 28 15:09:43 2023
tree7be5f9618179caf90df6d8e995199f5fbc3c0126
parentcd1ab1eb0ffd1b78d7c6449726bbfc96ce9a7c33 [diff]
Use new engine isLCPEvent helper

This CL takes advantage of the fact that we now store raw payloads and
can consequently get them and pass them into helpers we define
downstream.

It will get a little tricky because the helpeers downstream do not care
about frames and main frames; in Insights we leave the UI layer to
decide which events to show or not show, but in OPP that selection is
done in the data layer, so we still have to keep that logic around.
However this still will enable us to remove some logic from OPP that we
can defer to the new engine.

Bug: 1416836
Change-Id: Ifeab9092b779237ffb35807b70c324c6207e0a77
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4295034
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Andres Olivares <andoli@chromium.org>
7 files changed
tree: 7be5f9618179caf90df6d8e995199f5fbc3c0126
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .mailmap
  22. .npmignore
  23. .npmrc
  24. .style.yapf
  25. .stylelintignore
  26. .stylelintrc.json
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. DEPS
  31. LICENSE
  32. OWNERS
  33. package-lock.json
  34. package.json
  35. PRESUBMIT.py
  36. README.md
  37. tsconfig.json
  38. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

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