Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't debug node.js with integratedTerminal setting using MINGW64 #11778

Closed
akatechis opened this issue Sep 9, 2016 · 2 comments
Closed

Can't debug node.js with integratedTerminal setting using MINGW64 #11778

akatechis opened this issue Sep 9, 2016 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)

Comments

@akatechis
Copy link

  • VSCode Version: 1.5.1
  • OS Version: Windows 10 Home Edition

Steps to Reproduce:

  1. I have MINGW64 installed (the one bundled with the Git installer).
  2. I opened my node.js project in VSCode 1.5.1
  3. Set up a launch.json file as follows:
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Launch",
      "type": "node",
      "request": "launch",
      "program": "${workspaceRoot}/index.js",
      "stopOnEntry": false,
      "args": [],
      "cwd": "${workspaceRoot}",
      "preLaunchTask": null,
      "runtimeExecutable": null,
      "runtimeArgs": [
        "--nolazy"
      ],
      "env": {
        "NODE_ENV": "development"
      },
      "console": "integratedTerminal",
      "sourceMaps": false,
      "outDir": null
    }
  ]
}
  1. When I launch, I see a MINGW64 window open up, the directory is set correctly, but it's not doing anything, just waiting for me to type a command.
  2. After 10 seconds, the task in VSCode times out.

Things I've tried:

  1. Running npm start in cmd.exe, or in mingw works fine.
  2. Changing integratedTerminal to "externalTerminal" or "internalConsole" work fine.
@ramya-rao-a ramya-rao-a added the terminal Integrated terminal issues label Sep 9, 2016
@Tyriar Tyriar added the debug Debug viewlet, configurations, breakpoints, adapter issues label Sep 9, 2016
@Tyriar
Copy link
Member

Tyriar commented Sep 9, 2016

#8429 may be the cause of this

@weinand weinand added the bug Issue identified by VS Code Team member as probable bug label Apr 6, 2017
@Tyriar
Copy link
Member

Tyriar commented Apr 20, 2017

Duplicate #19334

@Tyriar Tyriar closed this as completed Apr 20, 2017
@Tyriar Tyriar added *duplicate Issue identified as a duplicate of another issue(s) and removed bug Issue identified by VS Code Team member as probable bug labels Apr 20, 2017
@weinand weinand removed the terminal Integrated terminal issues label Aug 23, 2017
@weinand weinand added the bug Issue identified by VS Code Team member as probable bug label Aug 23, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants