2

WEIRD HAPPENING.. I am unable to debug meteor app , BREAKPOINTS doesn't work in chrome(can see the server side sources thou).. I have already wasted 2 days over it ..

I have already tried Meteor: Debug on server side

Also tried similar options changing web-port and other options.

Also tried to reduce the node-inspector version, BUT breakpoints are not working for me..

any suggestions on how to debug this issue?

(Chrome browser, ubuntu, AMD machine, if that matters)

Community
  • 1
  • 1
shrw
  • 1,719
  • 5
  • 27
  • 50

3 Answers3

2

I have the same issue. The only workaround I've found is to put debugger; statements in my code. Those are respected and treated as breakpoints which stop the server for Node Inspector.

Geoffrey Booth
  • 7,168
  • 5
  • 35
  • 42
0

you can try observatory or read this article, maybe it'll helps

Ronald Pauffert
  • 4,346
  • 1
  • 14
  • 15
0

You are not alone. There is an issue posted to github about this, and it appears to be confirmed by several users.

I was able to get Node Inspector to work a while ago by downgrading to 1.10. It's not as nice as the new version but worked last time I used it. I honestly haven't needed it recently, but hopefully it'll still work.

rdickert
  • 560
  • 5
  • 14
  • The interface is different; is it possible you're overlooking the files? Under Scripts, there is a select box that when clicked will list all js files alphabetically. It will include all the Meteor files as well, but yours should be there. If there is nothing in the select box, then it's a different problem. – rdickert Nov 28 '13 at 16:26
  • Another possibility: are you setting NODE_OPTIONS. I'm assuming you are, since you could see your files before, but [there are instructions here](https://www.eventedmind.com/feed/6ed3ec0a-ac56-4fdb-8be0-f415c330d03c) if you need them. – rdickert Nov 28 '13 at 16:28
  • Github issue fixed and closed in July 2014. – bbsimonbb May 12 '15 at 13:24