Meteor debug kills the process on reload

I’ve had some success debugging meteor with vscode and the meteor debug approach or NODE_OPTIONS='--debug' meteor run. However, every hot code reload causes the meteor thread I’m debugging to be killed and started again. I need to reattach my debugger after ever reload.

Is this normal?

If I run meteor debug then the parent meteor process seems to use port 5858 and the child meteor process (which also gets restarted every code reload) exposes its debugger 5959. But I cannot connect any debugger to port 5858, although it does appear to be in use.

This is all on meteor, and I know there were some debugger issues fixed in 1.5.1, but unfortunately upgrading is not high on our priority list right now.

1 Like