[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 443cc1e549bc4606385a81d01b0a4e2d6e2ae5b5
commit443cc1e549bc4606385a81d01b0a4e2d6e2ae5b5[log] [tgz]
authorTim van der Lippe <tvanderlippe@chromium.org>Mon May 17 15:27:29 2021
committerCommit Bot <commit-bot@chromium.org>Tue May 18 10:07:14 2021
tree048e872cada8b2fec27c2bfedeb101f9b67c1bde
parentcc00c80523f22afe32b62fabea8143c755c49ba9 [diff]
Move CodeMirror types to third_party/codemirror

Some files that don't import codemirror itself do refer to types
as declared by CodeMirror, which therefore need to implicitly
side-effect import the types. The reason being that these files
are used in both the standalone and full version of CodeMirror
(depending on whether they run in a worker context or not).
Therefore, they can't import `third_party/codemirror/codemirror.ts`,
as that would only contain the full version.

DISABLE_THIRD_PARTY_CHECK=Tsc update
R=szuend@chromium.org

Bug: 1209844
Change-Id: I8719a15b40e9d9f085b24c05af4372ad84812d1f
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2897979
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Simon Zünd <szuend@chromium.org>
11 files changed
tree: 048e872cada8b2fec27c2bfedeb101f9b67c1bde
  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. .npmignore
  20. .npmrc
  21. .style.yapf
  22. .stylelintignore
  23. .stylelintrc.json
  24. ARCHITECTURE.md
  25. AUTHORS
  26. BUILD.gn
  27. DEPS
  28. LICENSE
  29. OWNERS
  30. package-lock.json
  31. package.json
  32. PRESUBMIT.py
  33. README.md
  34. tsconfig.base.json
  35. tsconfig.json
  36. 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