[ DWDS ] Serve DevTools from DDS by default (#2681)

In order to reduce the number of ways DevTools is served across the
ecosystem, we're working on serving DevTools from DDS by default in all
tools that spawn DDS.

This change exposes some new DDS related configuration options that
allow for specifying whether or not DevTools should be served via DDS
and whether or not an existing DevTools server should be used.

The `devToolsLauncher` parameter has been marked as deprecated as it
will be removed in a future major release, but will continue to act as
the default way to launch DevTools if it is provided. Other DDS related
properties that have been merged into the new
`DartDevelopmentServiceConfiguration` class are also marked as
deprecated.
23 files changed
tree: 8c7707280f9277f505c17571331a165ae8e36de7
  1. .github/
  2. _analysis_config/
  3. dwds/
  4. example/
  5. fixtures/
  6. frontend_server_client/
  7. frontend_server_common/
  8. test_common/
  9. tool/
  10. webdev/
  11. .gitattributes
  12. .gitignore
  13. AUTHORS
  14. CONTRIBUTING.md
  15. mono_repo.yaml
  16. README.md
README.md

Dart

Packages

PackageDescriptionVersion
dwdsA service that proxies between the Chrome debug protocol and the Dart VM service protocol.pub package
frontend_server_clientClient code to start and interact with the frontend_server compiler from the Dart SDK.pub package
webdevA CLI for Dart web development. Provides an easy and consistent set of features for users and tools to build and deploy web applications with Dart.pub package

Publishing automation

For information about our publishing automation and release process, see https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.