How to handle script errors in Durandal SPA

When you get a script error somewhere in your SPA code, the whole application becomes completely irrelevant, and you cannot go to other pages (views). Durandal seems to just freeze! (exit only - click update to start SPA again)

What are some good ways to handle these raw exception scenarios in a Durandal SPA?

Thoughts?

Thanks!

+7
source share
1 answer

My experience is to use Chrome as my main debugging tool, as I find the tools the easiest to use. However, from time to time, Durandal reports that an error has occurred. Not where and why it just stops and hangs, as you describe. Then I try the same in Firefox with the Firebug plugin. Then the browser usually stops the code in the right place.

I assume that you activated debug mode in your main.js?

0
source share

All Articles