Errors in template

Anytime there's an error in a template, I get a huge aurelia-lib stacktrace. It would be nice if it caught those, and added the view name that's causing the issue. Maybe maintain the context?

Start by reproducing an error in a template and tracing how the templating engine currently reports it. Done means the error identifies the view that caused it, preserves useful context, and avoids exposing an unhelpfully large aurelia-lib stack trace.

Written by the indexing model from the issue text.