Replies: 1 comment
-
We don't currently support it but if you're keen to add it, I'd suggest simply adding the option in the windows options and adding it here: Alternatively, you could back port this commit to v2: 459b5e1 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Does anybody know if it's possible, or a potential new feature to support passing these environment variables to the webview, so VSCode would attach? This would be a workflow improvement in my opinion, as opposed to the Browser Inspector GUI.
This is example of the environment variables set by VSCode Chrome Launcher
params.env['WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS'] =
--remote-debugging-port=${params.port}
;params.env['WEBVIEW2_WAIT_FOR_SCRIPT_DEBUGGER'] = 'true';
params.env['WEBVIEW2_PIPE_FOR_SCRIPT_DEBUGGER'] = pipeName;
Beta Was this translation helpful? Give feedback.
All reactions