jessicabyrne

I had the same problem. Turned out I had a call in my router.js that wasn't available anymore. When I removed it, the error went away.