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

args in launch.json not getting picked up. #2167

Closed
rkavalap opened this Issue Jan 22, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@rkavalap
Copy link

rkavalap commented Jan 22, 2016

I am trying with the below configuration. args for the program are not getting picked up. Is there something I am missing. ?
I am expecting something like "node node_modules/nightwatch/bin/runner.js --test buildOutput/JavaScript1.js --env devtest-chrome-win8" to be executed.
{
"version": "0.2.0",
"configurations": [
{
"name": "Launch",
"type": "node",
"request": "launch",
"program": "node_modules/nightwatch/bin/runner.js",
"stopOnEntry": false,
"args": [
"--test buildOutput/JavaScript1.js --env devtest-chrome-win8"
],
"cwd": ".",
"runtimeExecutable": null,
"runtimeArgs": [
"--nolazy"
],
"env": {
"NODE_ENV": "development"
},
"externalConsole": true,
"sourceMaps": false,
"outDir": null
},
{
"name": "Attach",
"type": "node",
"request": "attach",
"port": 5858
}
]
}

@weinand weinand added the debug label Jan 22, 2016

@weinand weinand self-assigned this Jan 22, 2016

@weinand

This comment has been minimized.

Copy link
Member

weinand commented Jan 22, 2016

@rkavalap you have to pass the arguments as individual string elements:

"args": [
   "--test", "buildOutput/JavaScript1.js",
   "--env", "devtest-chrome-win8"
]

@weinand weinand closed this Jan 22, 2016

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.