node.js, catching errors so script doesn't break?

Question

I have a node.js script and anytime an error happens node.js stops running with the error that happened.

What is the proper way of checking errors in node.js so it won't break the script and cause node.js to stop?

Fix your errors? Wrap code with potential run-time errors in try ... catch blocks? How is this different from any other language/interpreter? — nrabinowitz
– nrabinowitz, Commented Oct 13, 2011 at 23:16
@nrabinowitz So with try catch if an error occurs it wont break the script? And please forgive my lack of knowledge, very new to nodejs so its kind outside my comfort level. Trying to learn it. — John
– John, Commented Oct 13, 2011 at 23:21
yes, try ... catch in Javascript works the same way as in other languages, allowing you to catch and deal with errors in run-time code (though it won't help with parse-time errors, e.g. syntax errors). See developer.mozilla.org/en/JavaScript/Reference/Statements/… — nrabinowitz
– nrabinowitz, Commented Oct 13, 2011 at 23:41

rob · Accepted Answer · 2011-10-14 01:03:21Z

22

You can catch otherwise uncaught errors by setting the following:

process.on('uncaughtException', function (exception) {
   // handle or ignore error
  });

Of course, if you run your script in something like forever or node-supervisor, when your script "stops" it will start back up, which might solve your problem.

answered Oct 14, 2011 at 1:03

rob

10.2k7 gold badges44 silver badges73 bronze badges

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

3 Comments

Carlton Over a year ago

Really really handy...it was starting to get annoying checking my log files

Samson Over a year ago

Is this still recommended? are there side effects to this?

MattSidor Over a year ago

This method of error handling is strongly discouraged on the Joylet website. joyent.com/developers/node/design/errors

neowulf33 · Accepted Answer · 2013-07-23 21:07:33Z

3

Catching uncaughtException is no longer recommended.

Using domains are preferred. Using either "uncaughtException" or Domain, restarting the process is highly recommended after handling the exception.

To auto-restart the process, NodeJS provides another library called Cluster which assists in managing the worker threads.

answered Jul 23, 2013 at 21:07

neowulf33

6452 gold badges7 silver badges19 bronze badges

Collectives™ on Stack Overflow

node.js, catching errors so script doesn't break?

2 Answers 2

3 Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Linked

Related