It seems that when Aurelia encounters a problem compiling the views, we cannot get the exact trace of the error stack, but just an error regarding its consequence (it is impossible to load the view ...)
To try, write the wrong binding, for example, or use the wrong value converter: ... repeat.for = "elt in list" ...
And you will get, if this is your first glance:
"Router navigation error, and no previous location can be restored"
How to get a real stack trace, this lack of error management is very, very time consuming.
NB: Aurelia main.js is configured as follows:
aurelia.use
.standardConfiguration()
.developmentLogging();
source
share