Router logs 'no index.js found' for any MODULE_NOT_FOUND when loading routes

[taylortom]

When Router attempts to load a route (by require-ing index.js), if a MODULE_NOT_FOUND error is thrown, a generic 'no index.js found' message is logged. Depending on where the error's thrown, this could be caused by something else (e.g. missing local file, missing node module).

Steps to Reproduce

1. Require a node module that doesn't exist in a routes/index.js file.

Versions

• Authoring Tool Version: 0.4.0