Google Git
Sign in
chromium / devtools / devtools-frontend / 3ff5956c1e900cea33ebbe5d490d8a8f614b9623
commit3ff5956c1e900cea33ebbe5d490d8a8f614b9623[log] [tgz]
authorJack Franklin <[email protected]>Tue Apr 30 13:42:01 2024
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 30 14:15:05 2024
treee22ab9815ed91f77993ed8f6a0d3c6c7e36b8907
parentcea152005ec30d25c82f3d2f1de4967fdf7576cf [diff]
RPP: add experiment to run old engine

This will allow us to locally disable the old engine and check for
breakages, without the fear of breaking users. Once we are confident we
can make the change permanent and remove the old model.

Note that I named the experiment "Enable", rather than "Disable", to
avoid a confusing double negative. But the experiment is enabled by
default, so the default experience for users here is to run the old
engine.

Bug: 40287735
Change-Id: I2eeefc1d3815f7a0dfcb43ba1eb3cf460c3176af
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5497335
Auto-Submit: Jack Franklin <[email protected]>
Reviewed-by: Andres Olivares <[email protected]>
Commit-Queue: Jack Franklin <[email protected]>
5 files changed
tree: e22ab9815ed91f77993ed8f6a0d3c6c7e36b8907
  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. .eslintignore
  19. .eslintrc.js
  20. .git-blame-ignore-revs
  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. DEPS
  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 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