Google Git
Sign in
chromium / devtools / devtools-frontend / b96b1b6f996c61a502ad60150c54a557bc853265
commitb96b1b6f996c61a502ad60150c54a557bc853265[log] [tgz]
authorSimon Zünd <szuend@chromium.org>Fri Aug 23 07:47:30 2024
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Aug 23 08:49:02 2024
tree811f3f7c0fb681615c422fb547d85ddc2b8f68ac
parentf18cb915d85815f3f5b3a97c34e1a1160b2a5557 [diff]
[esbuild] Use correct tsconfig.json to build

ESBuild used the root tsconfig.json which is only intended for
VSCode. This still mostly works as we have a "base" tsconfig.json that
acts as the source of truth for the different compiler options
globally.

This CL updates ESBuild to use the per ts_library invocation
generatd tsconfig.json instead.

R=pfaffe@chromium.org

Fixed: 352249693
Change-Id: I6936f66b2e2f78aa7971dc2158076d697dc15553
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5804333
Commit-Queue: Simon Zünd <szuend@chromium.org>
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
1 file changed
tree: 811f3f7c0fb681615c422fb547d85ddc2b8f68ac
  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. .gitallowed
  22. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .gn
  26. .mailmap
  27. .npmignore
  28. .npmrc
  29. .style.yapf
  30. .stylelintignore
  31. .stylelintrc.json
  32. AUTHORS
  33. BUILD.gn
  34. codereview.settings
  35. CONTRIBUTING.md
  36. DEPS
  37. favicon.ico
  38. LICENSE
  39. OWNERS
  40. package-lock.json
  41. package.json
  42. PRESUBMIT.py
  43. README.md
  44. tsconfig.json
  45. 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 Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

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

There are a few options to keep an eye on the latest and greatest of DevTools development: