Google Git
Sign in
chromium / devtools / devtools-frontend / 2957dc8af0f8bfb0c9b7bf1d5c76ce5e0e9eb66f
commit2957dc8af0f8bfb0c9b7bf1d5c76ce5e0e9eb66f[log] [tgz]
authorTim van der Lippe <[email protected]>Tue Jul 14 10:22:11 2020
committerCommit Bot <[email protected]>Tue Jul 14 13:07:26 2020
treef2b1320e3a7cafdc6e837bb77ef1783da143b6ec
parentb9f308bca2689e501c2b1cacfb1c1059de406f16 [diff]
Move data_deps to front_end

Since `devtools_{entrypoint,module}` now properly use the data_deps
to move data over to isolates on CQ, we can move these back into
the proper location of `front_end/BUILD.gn`

[email protected]

Bug: 1101738
Change-Id: I858d863471df549e6b19b23ab41b1ff4d189e40c
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2295861
Commit-Queue: Paul Lewis <[email protected]>
Reviewed-by: Paul Lewis <[email protected]>
Auto-Submit: Tim van der Lippe <[email protected]>
4 files changed
tree: f2b1320e3a7cafdc6e837bb77ef1783da143b6ec
  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_files.gni
  23. all_devtools_modules.gni
  24. AUTHORS
  25. BUILD.gn
  26. COMMON_OWNERS
  27. DEPS
  28. devtools_module_entrypoints.gni
  29. ENG_REVIEW_OWNERS
  30. INFRA_OWNERS
  31. LICENSE
  32. LIGHTHOUSE_OWNERS
  33. OWNERS
  34. package-lock.json
  35. package.json
  36. PRESUBMIT.py
  37. protocol.json
  38. README.md
  39. tsconfig.base.json
  40. tsconfig.json
  41. 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