After quite a bit of debugging we found that the issue was caused by the customized ribbon. We had a button we added to the ribbon that was calling into a javascript library. What was left off was the $webresource directive.
Hopefully this helps someone, the errors thrown for this do not help debug the root cause.