You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
Please add support for nodebug : true parameter (Run mode - launch with ctrl+f5, see https://code.visualstudio.com/docs/editor/debugging#_run-mode). It was implemented in microsoft/vscode#2780. This should simple launch Chrome with specified url, without any debuger attaching, so we can use for examples dom inspector, debug css styles or use integrated debugger, which is sometimes better option.
Copied from original issue: Microsoft/vscode-chrome-debug#220
The text was updated successfully, but these errors were encountered:
Can we abstract this away in a some generic launch logic, where each debugger vscode-chrome-debug and vscode-edge-dubug simply provide the runtime executable and arguments?
Thinking this could be relevant for Electron, Edge, iOS, etc.
It might be easier for extensions to launch their own process then just check if (args.noDebug) before attaching to it. That's the only difference. Might be able to save them a call to spawn but it's not saving much.
From @jan-zajic on September 2, 2016 8:39
Please add support for nodebug : true parameter (Run mode - launch with ctrl+f5, see https://code.visualstudio.com/docs/editor/debugging#_run-mode). It was implemented in microsoft/vscode#2780. This should simple launch Chrome with specified url, without any debuger attaching, so we can use for examples dom inspector, debug css styles or use integrated debugger, which is sometimes better option.
Copied from original issue: Microsoft/vscode-chrome-debug#220
The text was updated successfully, but these errors were encountered: