Stop building formatter_worker-entrypoint with build_release_applications

This moves the formatter_worker-entrypoint out of the
build_release_application inputs. That's because this module is now
standalone and fully typechecked by TypeScript.

This also removes its legacy `module.json` support and stops using
the RuntimeInstantiator to start the entrypoint. That's possible,
because `formatter_worker` only relies on JavaScript files, which
the static imports already perform the loading for. The only
replacement is the `self.postMessage` which was previously performed
by the `startWorker` function in `RuntimeInstantiator`.

R=aerotwist@chromium.org

Change-Id: Icd18c0f16b42b9246ea138a9a68cbb06fd7e192b
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2302603
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Paul Lewis <aerotwist@chromium.org>
9 files changed
tree: ce9ccc0d3388ebbe0ee9ae52eccd595a21e82cd5
  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_image_files.gni
  29. devtools_module_entrypoints.gni
  30. ENG_REVIEW_OWNERS
  31. INFRA_OWNERS
  32. LICENSE
  33. LIGHTHOUSE_OWNERS
  34. OWNERS
  35. package-lock.json
  36. package.json
  37. PRESUBMIT.py
  38. protocol.json
  39. README.md
  40. tsconfig.base.json
  41. tsconfig.json
  42. 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