Support running (via daemon) without the need to spawn Chrome with dev flags
- Dominant language
- Dart
- Stars
- 224
- Forks
- 94
- Avg merge
- 7h 14m
- Merged PRs (30d)
- 2
Description
We briefly discussed this somewhere, but I don't think there's an open issue to track it. To support [some setups](https://code.visualstudio.com/docs/remote/remote-overview), we'd need to be able to run webdev on a remote machine (or in a container) without spawning the browser, then connect our own browser. This means webdev would have no connection to the Chrome debugger protocol.
As well as the general remote support, it seems likely [VS Code Online](https://techcrunch.com/2019/05/06/microsoft-launches-visual-studio-online-an-online-code-editor/) support would be enabled by this too.
Contributor guide
Research direction
No files or tests are named. Start by tracing the daemon's browser-spawning and connection setup, then determine how an externally managed browser would connect; done means webdev can run remotely or in a container without spawning Chrome or using the Chrome debugger protocol.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100