- This topic has 20 replies, 4 voices, and was last updated 6 years, 6 months ago by
.
-
Posts
-
Davide,
Thank you for the kind words – I’ve passed them on to our teams; it’s always great to hear positive feedback about a product we’re all working very hard on.
Do keep the feedback coming – as you can see, we’re listening!
Since some days I have problems attaching the debugger to my nodejs on port 5858.
When I try to launch the codemix debugger, it says nothing and it does nothing.
If I use the same launch.json on visual studio code, it works well.Is there some regression here?
Thanks.Davide,
No regression that we know of – I’ll get a more detailed test tomorrow.
1) Can you share your
launch.jsonfile?
2) Check the Error Log view for errors logged when you try to initiate the debugging session.
3) Can you check the Debug view (in the Debug perspective) to see if some debug session is at least being initiated (but perhaps nothing beyond that is working?)
4) Are you breakpoints in JavaScript or in TypeScript?1) launch.json
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
“version”: “0.2.0”,
“configurations”: [
{
“type”: “node”,
“request”: “attach”,
“name”: “Attach”,
“port”: 5858
}
]
}
2) error log is empty3) no session initiated
4) javascript
Davide,
We tried with a similar launch configuration and had no issues debugging Node applications. Also, can you let us know what version of Node you’re debugging against – could there have been a change there between the time it was working an not?
Do check your log again and your Console (in the Console view, use the drop down to switch to the Debug console and see if there is any output there).
The last thing I can think of is if the outbound connection is being blocked by the windows firewall, those settings may have changed.
