node.js debugging with source line numbers

Question

Similar questions has been asked, I went through 'how to debug node' threads, but those are however either old or not about the problem i got.

Problem:

I'm writing some small tools in node.js stack - and my debugging experience is quite frustrating: when an exception is thrown, in many cases I get very annoying messages like the one here:

TypeError: Bad argument

wtf? it's neither verbose or useful - no source line number, no information in which file this exception was thrown.

Question:

How do I get my console to output usefull information when exceptions/errors are thrown and console.log function has something to say. would be great to have a simple console.log call where it actually puts a line number and maybe a file name where the message happens.

I don't know how to track the info you want on console but debugging is very easy with WebStorm IDE. I recommend it. — Snow Blind
– Snow Blind, Commented Jul 27, 2013 at 13:21
Use one of the debugging approaches from here: stackoverflow.com/questions/12641679/… — JohnnyHK
– JohnnyHK, Commented Aug 3, 2014 at 13:21

uSide · Accepted Answer · 2013-07-27 14:05:07Z

2

in nodejs i use this function to see error stack:

process.on('uncaughtException', function(err) {
    console.log(err.stack);
})

answered Jul 27, 2013 at 14:05

uSide

362 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

numediaweb · Accepted Answer · 2014-08-03 13:08:29Z

0

Use the --stack option to see stack traces. Such as grunt task --stack

answered Aug 3, 2014 at 13:08

numediaweb

17.2k12 gold badges79 silver badges117 bronze badges

Collectives™ on Stack Overflow

node.js debugging with source line numbers

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related