-
-
Notifications
You must be signed in to change notification settings - Fork 536
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
debug-wise args are not honored #531
Comments
Continuation of discussion of remy/nodemon#1250 and specifically remy/nodemon#1250 (comment). |
Yes, I was going crazy for a file. I thought it was just me. Actually, I am also running nodemon but I took this out of the equation. So I execute
And the same thing, it never waits for the debugger to be attached and prints out to the console the console.log that I made. I also had a breakpoint on the console.log. |
Sorry, probably worth mentioning that i am on a MAC and ts-node v4.1.0 |
Ok, I think i have a workaround You can execute it like this
so you can create your nodemon.json file and do this, (create multiple nodemon.json files if you like - I have 1 for inspect and 1 for inspect-brk)
Hope that helps. So this trick here is not to run ts-node direct but to load via node. |
@appsolutegeek Thanks for the workaround! Unfortunately it's not a complete solution because there's a case when third-party tools pass these args to the ending dynamically, e. g. Visual Studio Code debugger. |
I'd recommend using |
Closing with #536. I recommend |
nodemon -v
: 1.14.12node -v
: 8.9.4ts-node -v
: 4.1.0nodemon
with the followingnodemon.json
:Expected behaviour
--inspect=5858 --inspect-brk
are passed to node and one can connect with debuggerActual behaviour
--inspect=5858 --inspect-brk
are not passed to node and one can't connect with debuggerterminal output:
Steps to reproduce
yarn install
ornpm install
yarn run serve:debug
ornpm run serve:debug
Attach to nodemon
VS Code debug configurationThe text was updated successfully, but these errors were encountered: