Related
Lone Ranger I'm trying the newly released preview of Visual Studio Code on Mac OS X and I get the error "Cannot start OpenDebug due to Mono (or Mono version >= 3.10.0) when trying to start debugging or attaching to my node.js app , so OpenDebug cannot be start
Lone Ranger I'm trying the newly released Visual Studio Code preview on Mac OS X and I get the error "Cannot start OpenDebug due to Mono (or Mono version >= 3.10.0, Therefore cannot start OpenDebug)) is required". I have installed Mono MDK from http://www.mono
Lone Ranger I'm trying the newly released Visual Studio Code preview on Mac OS X and I get the error "Cannot start OpenDebug due to Mono (or Mono version >= 3.10.0) when trying to start debugging or attaching to my node.js app , so OpenDebug cannot be started)
Lone Ranger I'm trying the newly released preview of Visual Studio Code on Mac OS X and I get the error "Cannot start OpenDebug due to Mono (or Mono version >= 3.10.0, Therefore cannot start OpenDebug)) is required". I have installed Mono MDK from http://www.m
Jacabello I tried to debug the project in node JS using Visual Studio Code but it didn't work. I built a simple project with: express myExpressApp cd myExpressApp npm install npm start My file launch.json: I select the "Launch app.js" option in the "Debug" win
Jacabello I tried to debug the project in node JS using Visual Studio Code but it didn't work. I built a simple project with: express myExpressApp cd myExpressApp npm install npm start My file launch.json: I select the "Launch app.js" option in the "Debug" win
Vinianski How to debug child Node.JS processes in VS Code? Here is an example of the code I am trying to debug: var spawn = require('child_process').spawn;
var scriptPath = './child-script.js';
var runner_ = spawn('node', [scriptPath]);
Benjamin Passero You c
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Basil Battikhi I have a loop that has a huge iteration of about 300 iterations, which may be small, but I'm having trouble debugging the loop, let's look at the code below (example, it's not exactly part of the code) . const myVar = [
{ name: 'basil', age: 2
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Vinianski How to debug child Node.JS processes in VS Code? Here is an example of the code I am trying to debug: var spawn = require('child_process').spawn;
var scriptPath = './child-script.js';
var runner_ = spawn('node', [scriptPath]);
Benjamin Passero You c
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Basil Battikhi I have a loop that has a huge iteration of about 300 iterations, which may be small, but I'm having trouble debugging the loop, let's look at the code below (example, it's not exactly part of the code) . const myVar = [
{ name: 'basil', age: 2
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Brutus I'm currently trying to debug a Node JS application written in TypeScript from Visual Studio Code and I'm running into some issues. I have a situation similar to the one described in this question |-- .settings
|----- launch.json
|-- bin
|----- app.js
|
Basil Battikhi I have a loop that has a huge iteration of about 300 iterations, which may be small, but I'm having trouble debugging the loop, let's look at the code below (example, it's not exactly part of the code) . const myVar = [
{ name: 'basil', age: 2
Vinianski How to debug child Node.JS processes in VS Code? Here is an example of the code I am trying to debug: var spawn = require('child_process').spawn;
var scriptPath = './child-script.js';
var runner_ = spawn('node', [scriptPath]);
Benjamin Passero You c
Angelo Using Visual Studio Code Version 1.13.0, when launching node to debug test2.js, the node is version 0.12 with the following configuration, I can debug and the response from vscode is: Debugging with legacy protocol because it was detected.
But when nod
Angelo Using Visual Studio Code Version 1.13.0, when launching node to debug test2.js, the node is version 0.12 with the following configuration, I can debug and the response from vscode is: Debugging with legacy protocol because it was detected.
But when nod
Angelo Using Visual Studio Code Version 1.13.0, when launching node to debug test2.js, the node is version 0.12 with the following configuration, I can debug and the response from vscode is: Debugging with legacy protocol because it was detected.
But when nod
Angelo Using Visual Studio Code Version 1.13.0, when launching node to debug test2.js, the node is version 0.12 with the following configuration, I can debug and the response from vscode is: Debugging with legacy protocol because it was detected.
But when nod
Angelo Using Visual Studio Code Version 1.13.0, when launching node to debug test2.js, the node is version 0.12 with the following configuration, I can debug and the response from vscode is: Debugging with legacy protocol because it was detected.
But when nod
Jacob Jeske I'm new to OS X (4 days with a new Mac) and I'm trying to set up an environment where I can debug an Asp.Net 5 web project locally using the debugger built into Visual Studio Code. Breakpoints that work when attached to mono. I followed these instr
Jacob Jeske I'm new to OS X (4 days with a new Mac) and I'm trying to set up an environment where I can debug an Asp.Net 5 web project locally using the debugger built into Visual Studio Code. Breakpoints that work when attached to mono. I followed these instr
Crude I want to jump into python code as soon as nodejs creates subprocess to debug python code Server.js： const spawn = require("child_process").spawn;
const pythonProcess = spawn('python',["MyPythonFile.py"]);
console.log("Finished!")
MyPythonFile.py： print