Has anyone here gotten a working VSCode `launch.js...
# orm-helpd
devan
12/11/2018, 8:39 PMHas anyone here gotten a working VSCode
launch.jsonp
Priyank Patel
12/11/2018, 8:43 PMThis is something I started to work on last night but didn't get time to finish the configuration. https://github.com/Microsoft/vscode/issues/40430 Maybe this will be of help?
d
devan
12/11/2018, 8:54 PMInteresting. I tried the latest comment’s setup, and got it running successfully, but the debugger couldn’t attach to the port, oddly enough. You run across the same thing?
devan
12/11/2018, 8:56 PM Copy code
{
"name": "Launch via nodemon",
"type": "node",
"request": "launch",
"protocol": "inspector",
"cwd": "${workspaceFolder}",
"runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nodemon",
"runtimeArgs": [
"--exitcrash",
"-e",
"ts,graphql",
"-x",
"${workspaceRoot}/node_modules/.bin/ts-node"
],
"args": [
"${workspaceRoot}/src/index.ts"
],
"restart": true,
"console": "integratedTerminal",
"internalConsoleOptions": "openOnSessionStart",
"skipFiles": [
"node_modules/**",
"<node_internals>/**"
]
}p
Priyank Patel
12/11/2018, 8:58 PMI am going to try it in few hours, at work right now. I am having a weird issue where any changes to the TS file would automatically start the server without any log. It's bit frustrating as I can't seem to find the cause of it.
d
devan
12/11/2018, 9:31 PMCurious if you are able to get it working. I haven’t found a way to debug in my graphql server other than console.log 🙈
p
Priyank Patel
12/11/2018, 11:54 PMI got it working. Place these 2 files inside .vscode.
Priyank Patel
12/11/2018, 11:54 PMPriyank Patel
12/11/2018, 11:54 PMPriyank Patel
12/11/2018, 11:55 PMLet me know if this configuration works for you.
d
devan
12/11/2018, 11:56 PMInteresting. Are you using nodemon and TS-Node? Or straight TypeScript compiler?
p
Priyank Patel
12/12/2018, 12:44 AMPriyank Patel
12/12/2018, 12:44 AMPriyank Patel
12/12/2018, 12:45 AMlaunch.json is inside .vscode. config.json is in root folder and add
"start:inspect": "nodemon --config config.json"Priyank Patel
12/12/2018, 12:45 AMyou can either run using npm npm run start:inspect or yarn yarn start:inspect
Priyank Patel
12/12/2018, 12:46 AMOnce you have the server running, you can switch the debugger config to Attach and it should bind to localhost:5858 which the inspector is running on.
Priyank Patel
12/12/2018, 12:46 AMI can't seem to toggle any breakpoints tho. Let me know if it works for you.
d
devan
12/12/2018, 9:06 AMI got it all figured out on my end.
I can start the debugger one of two ways:
devan
12/12/2018, 9:07 AM1. Using the VSCode Debugger Extension, I can run the “Launch and Debug” task:
devan
12/12/2018, 9:08 AM Copy code
{
"name": "Launch and Debug",
"type": "node",
"request": "launch",
"protocol": "inspector",
"cwd": "${workspaceFolder}",
"runtimeExecutable": "${workspaceFolder}/node_modules/.bin/dotenv",
"runtimeArgs": [
"--",
"${workspaceRoot}/node_modules/.bin/nodemon",
"-e",
"ts,graphql",
"-x",
"node"
],
"args": [
"-r",
"ts-node/register",
"src/index.ts"
],
"restart": true,
"console": "integratedTerminal",
"internalConsoleOptions": "openOnSessionStart",
"skipFiles": [
"node_modules/**",
"<node_internals>/**"
]
}devan
12/12/2018, 9:08 AMOr 2. I can execute a debug script and then use a launch.json config to attach:
devan
12/12/2018, 9:09 AM"start:debug": "dotenv -- nodemon -e ts,graphql -x node --inspect -r ts-node/register src/index.ts",devan
12/12/2018, 9:09 AM Copy code
{
"type": "node",
"request": "attach",
"name": "Attach to Process",
"port": 9229,
"restart": true,
"protocol": "inspector"
},devan
12/12/2018, 9:09 AMBreakpoints are working for me.
👍 1
3 Views