Google Git
Sign in
chromium / devtools / devtools-frontend / refs/heads/chromium/6166
commit1a0e8dbcc06a90339b858924a7facc6a96ca609b[log] [tgz]
authorJack Franklin <[email protected]>Mon Dec 04 11:35:15 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Dec 04 11:57:33 2023
tree992b8fa956f764fd57801ccd3e606d9a0cf4637f
parentc81ff32bd3ea8cca33e39167b1449077f152755e [diff]
Use `typeRoots` for custom type-defs

crrev.com/c/5081999 added in custom WebGPU types, however doing so via
`types:[]` overrides the TS default behaviour to include types from
`node_modules/@types`. This means in VSCode/LSP based editors, we now
get TS errors in tests from `assert` and `sinon`, which TS now cannot
detect (as it is not reading `node_modules/@types/...`).

To prevent this we can instead use `typeRoots`, and specify the folders
to use. This maintains the default behaviour and adds detection of the
WebGPU types.

Bug: 1506431
Change-Id: Ie5aed47bc630852305ecc101d05d7081dfa71647
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5083022
Reviewed-by: Simon Zünd <[email protected]>
Commit-Queue: Jack Franklin <[email protected]>
2 files changed
tree: 992b8fa956f764fd57801ccd3e606d9a0cf4637f
  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