I have tried using both 1.6 and 1.6.1 for the below
I recently moved to a new windows laptop, installed meteor (x64 arch)
using Chrome Version 66.0.3359.139 (Official Build) (64-bit). Previously was using 65.0.3325 Chrome. (It was also working fine on my old machine.)
i’m able to go to chrome://inspect, open up the Node Inspector. All the server side files are there. Can click to set breakpoints. But they never get hit.
client side breakpoints get hit just fine.
am at a complete loss for how to fix this. is freezing development. any ideas?
Started using vscode.
Run it in the terminal after setting it up… using
Meteor run --inspect --settings …/path/to file
Don’t run it with the green arrow.
Make sure auto attach is on, bottom left corner.
Might have to click cancel on some timeouts, and run it 2-3 times before all pieces sync up.
Seems like a WIP, but reliable once you get it going.
The link you provided is about how to use vs-code to debug meteor. This thread is about using the native chrome debugger (chrome://inspect) to debug meteor server applications.
I’m still having this problem, for anyone still struggling to debug server side, the only way it works for me it to set the breakpoints with the debugger; keyword in code
Same problem. I tried different setups with Chrome and VSCode, but in both my breakpoints get completely ignored. debugger; helped to stop chrome, but is not flexible enough for a real debug.
EDIT: Turns out debugger; will stop correctly, but afterwards I can’t step through the code line by line. Hitting step over next function call has the same effect as resume execution… So debugging is completely broken for me