Hacker News Reader

Logging errors to the console can be helpful to find them during debugging/development (as opposed to having them fail silently).

The goal isn't to leave errors in, its to expose them when something changes to make them happen so that you can do the 2 things above.

View on HN

You need to configure or change your promise implementation if uncaught errors fail silently.

In any case, logging error gives you no information anyway. Just try running: `console.log(new Error("..."))`. So at the very least you should do `catch(function(e){console.log(e.stack);})`

You can just crash (and still see the stacktrace) and automatically restart. You shouldn't leave these `catch/ignore` in your code in prod, this is a pretty good way to get undefined behaviors and maybe corrupted data.

Reply on news.ycombinator.com