Move all_devtools_modules to separate gni file

This allows us to give COMMON_OWNERS edit access, while all other
build scripts remain INFRA_OWNERS access. Moreover, this should
make reading and traversing /BUILD.gn easier.

DISABLE_THIRD_PARTY_CHECK=Add owner access to new file

Bug: 1097043
Change-Id: Ic2d9cfa89bc6f24b7b89817d1118f5b5ffb2d188
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2256982
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
4 files changed
tree: e37418bd79f1774f7f524ebe5a1638f00f929e43
  1. back_end/
  2. build_overrides/
  3. docs/
  4. front_end/
  5. node_modules/
  6. scripts/
  7. test/
  8. third_party/
  9. v8/
  10. .clang-format
  11. .editorconfig
  12. .eslintignore
  13. .eslintrc.js
  14. .gitattributes
  15. .gitignore
  16. .gn
  17. .npmignore
  18. .npmrc
  19. .style.yapf
  20. .stylelintignore
  21. .stylelintrc.json
  22. all_devtools_modules.gni
  23. AUTHORS
  24. BUILD.gn
  25. COMMON_OWNERS
  26. DEPS
  27. ENG_REVIEW_OWNERS
  28. INFRA_OWNERS
  29. LICENSE
  30. LIGHTHOUSE_OWNERS
  31. OWNERS
  32. package-lock.json
  33. package.json
  34. PRESUBMIT.py
  35. protocol.json
  36. README.md
  37. tsconfig.base.json
  38. tsconfig.json
  39. 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.

Design guidelines

Please be aware that DevTools follows additional development guidelines.

Issue triage

The issue triage guidelines can be found here.

Workflows

Instructions to set up, use, and maintain a DevTools frontend checkout can be found here.

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