Don't assume all routes are handled in Angular

> The routeChangeSuccess event listener assumes that there will be a route. This
is not the case if the current route isn't defined by Angular and can result in
JavaScript errors.

I'm working on a very large web application where only particular views are handled by Angular (the rest are handled by a legacy system and in these cases `$routeChangeSuccess` fires with an `undefined` `route`)