Closed conradoGen closed 4 months ago
it always starts the terminal as
This is intended since VS Code sets environment variables for the process.
What's the bug?
How should we run without attaching the debugger?
From: Connor Peet @.> Sent: 25 June 2024 23:21 To: microsoft/vscode-js-debug @.> Cc: Thiago Conrado @.>; Author @.> Subject: Re: [microsoft/vscode-js-debug] autoattach not working: cannot run without debugger if using launch.json (Issue #2025)
it always starts the terminal as
This is intended since VS Code sets environment variables for the process.
What's the bug?
— Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode-js-debug/issues/2025#issuecomment-2190413915, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BGDHYJZW3SCIW2VB3WZ2YHLZJIQUBAVCNFSM6AAAAABJ4ZZJMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJQGQYTGOJRGU. You are receiving this because you authored the thread.Message ID: @.***>
Describe the bug A clear and concise description of what the bug is.
To Reproduce vscode launch { "type": "node", "request": "launch", "name": "Update Examples", "program": "${workspaceFolder}/dist/util/runUpdateEgWithDB.js", "console": "integratedTerminal", "env": { "WRITE_RESPONSE_TO_FILE": "true", "NODE_OPTIONS": "", "VSCODE_INSPECTOR_OPTIONS": "" }, "restart": false, "autoAttachChildProcesses": false, "sourceMaps": false },
it always starts the terminal as
cd /home/xzz/zzzz/privacy-relay ; /usr/bin/env WRITE_RESPONSE_TO_FILE=true 'NODE_OPTIONS= --require /home/xzz/.vscode-server/bin/5437499feb04f7a586f677b155b039bc2b3669eb/extensions/ms-vscode.js-debug/src/bootloader.js --inspect-publish-uid=http' 'VSCODE_INSPECTOR_OPTIONS=:::{"inspectorIpc":"/tmp/node-cdp.582085-fb8a4243-16.sock","deferredMode":false,"waitForDebugger":"","execPath":"/usr/local/bin/node","onlyEntrypoint":true,"autoAttachMode":"always","mandatePortTracking":true,"fileCallback":"/tmp/node-debug-callback-9d192041cb9a41ec"}' /usr/local/bin/node ./dist/util/myFile.js
also, makes no difference running with ctrl + f5 vs f5