external_handlers.dartdart ../devtools/bin/devtools.dart --vm-uri VM_Auth_URI--profile-memoryFileName --verbose VM_Auth_URI - token displayed in flutter run e.g., http://127.0.0.1:37141/m6a1twmdRpI=/FileName - location and file name to store statistics e.g., /usr/local/home/myname/Downloads/memory_samples.jsonpackage:sse.~/.devtools.logScreenView.logScreenView.hostname.http_multi_server for serving.package:vm_service (1.2.0).package:vm_service (1.1.1).launchDevTools service will now register with VMs using public APIs when available, falling back to private APIs otherwise.launchDevTools service will now return well-formed errors if it fails to launch the browser for any reason.launchDevTools service will now launch the native ChromeOS browser (instead of the Linux version of Chrome installed in the Linux container) if both the DevTools and VM Service ports are accessible (tunneled) to the ChromeOS browser.vm.register which allows registering of VM services:{
"id":"1",
"method":"vm.register",
"params":{
"uri":"<vm-service-uri-here>",
}
}
DevTools will connect to each registered VM and register a launchDevTools service that can then be called (via the VM service protocol). The arguments to this service can include a queryParams object that will be used to build the querystring:{
queryParams: {
hide: "debugger",
theme: "dark",
},
}