jmcannon
Results
3
comments of
jmcannon
If I revert to a previous commit (June 26, 2015, for example), it fixes this problem. EDIT: it looks like 65acd700e773ba4bf9700b35535f05234cfc349d is the culprit. Unfortunately, the diff is too big...
Nope, I can't figure it out. Just living with the error always being in my console for now.
Yes, I think you're right. I just fell back to the default Next serverless environment.