Skip to content

Support running DWDS without a Chrome Debug Port #2605

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bkonyi opened this issue Apr 2, 2025 · 0 comments
Open

Support running DWDS without a Chrome Debug Port #2605

bkonyi opened this issue Apr 2, 2025 · 0 comments
Assignees
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures package:dwds triaged

Comments

@bkonyi
Copy link
Collaborator

bkonyi commented Apr 2, 2025

In certain circumstances we're unable to get access to a Chrome Debug Port to communicate with the Chrome debugger (e.g., when an application is embedded in VSCode, running via the web-server device in Flutter where the application is accessed via a non-Chrome browser) but DWDS support is still needed to provide support for non-debugger related developer tooling (e.g., hot reload, service extension handling).

The DWDS requirement for a Chrome Debug Port should be removed and DWDS should instead provide a limited set of functionality when it doesn't have access to the Chrome debugger.

@bkonyi bkonyi added P1 A high priority bug; for example, a single project is unusable or has many test failures package:dwds triaged labels Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures package:dwds triaged
Projects
None yet
Development

No branches or pull requests

2 participants