[go: nahoru, domu]

Update //third_party/pyjson5/OWNERS.

Apparently I missed this file when I switched from
'dpranke@chromium.org' to 'dpranke@google.com' everywhere else.

Bug: chromium:1215425
Change-Id: If369db82df08fff37498a442df82032b2bc4b0d5
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2933220
Commit-Queue: Dirk Pranke <dpranke@google.com>
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Auto-Submit: Dirk Pranke <dpranke@google.com>
Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org>
1 file changed
tree: 5272da51f5f0621d9970d4aab5fadc67b6f7c849
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. front_end/
  6. inspector_overlay/
  7. node_modules/
  8. scripts/
  9. test/
  10. third_party/
  11. v8/
  12. .clang-format
  13. .editorconfig
  14. .eslintignore
  15. .eslintrc.js
  16. .gitattributes
  17. .gitignore
  18. .gn
  19. .mailmap
  20. .npmignore
  21. .npmrc
  22. .style.yapf
  23. .stylelintignore
  24. .stylelintrc.json
  25. ARCHITECTURE.md
  26. AUTHORS
  27. BUILD.gn
  28. DEPS
  29. LICENSE
  30. OWNERS
  31. package-lock.json
  32. package.json
  33. PRESUBMIT.py
  34. README.md
  35. tsconfig.base.json
  36. tsconfig.json
  37. 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 in docs/triage_guidelines.md.

Workflows

Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.

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