@christopherfujino FWIW this flag was used by VS Code, and now flutter daemon --show-web-service-device (which is configured by the "dart.flutterShowWebServerDevice" setting) just terminates and results in this:

Is it possible we can keep this flag as a no-op for a while?

(btw, it was my understanding that this flag had been added specifically to hide the web-server device for most users, because they would select it instead of Chrome in the IDE and then get stuck because they didn't understand the flow with the Dart Debug extension - have opinions around this changed?)

(btw, it was my understanding that this flag had been added specifically to hide the web-server device for most users, because they would select it instead of Chrome in the IDE and then get stuck because they didn't understand the flow with the Dart Debug extension - have opinions around this changed?)

Ahh, what happened was no one we asked remembered this context. Let me revert for now to unblock dart-code and so we can discuss whether or not we're concerned about confusing dart debug extensions users.

@christopherfujino np! Let me know if you do decide to go ahead with it and I can migrate Dart-Code off it for relevant versions (although, we should retain the flag for a little while as a no-op to help the transition for older plugins).

@christopherfujino np! Let me know if you do decide to go ahead with it and I can migrate Dart-Code off it for relevant versions (although, we should retain the flag for a little while as a no-op to help the transition for older plugins).

Yes, definitely, both on keeping you involved in the discussion and about migrating the command to be no-op. I should have made it no-op in the first place, but I assumed nobody ever used this flag :P

but I assumed nobody ever used this flag :P

To be fair, this flag isn't passed by default in Dart-Code for most users. You either have to opt-in, or be running in a remote workspace (where we assume web-server is probably what you need and not Chrome, because if we spawn Chrome you might not see it). So not a massive break, but definitely non-zero :-)

but I assumed nobody ever used this flag :P

To be fair, this flag isn't passed by default in Dart-Code for most users. You either have to opt-in, or be running in a remote workspace (where we assume web-server is probably what you need and not Chrome, because if we spawn Chrome you might not see it). So not a massive break, but definitely non-zero :-)

ahh yes, I did know about the remote workspace workflow--but forgot.