You can reproduce the problem using the with-custom-babel-config example with [email protected]. There is no issue using next@latest.
https://github.com/zeit/next.js/pull/1344/files should work 馃
Will be a very happy camper once this is resolved; our testing is blocked and downgrading will re-introduce other issues.
Narrowed it down a bit; 3.0.0-beta6 works and 3.0.0-beta8 doesn't. Here's the difs.
This should not be happening. But I'll check this.
@arunoda Found the exact issue. The difference that caused it was upgrading Webpack to 2.6. Maybe upgrading Webpack would fix it?
Just noticed that for some reason the webpack entry in package.json is missing the ^. This is locking it to 2.6.0 鈥撀爐he patch we need is in 2.6.1.
Seeing the same issue with webpack v3.4.1 in IE11.
ReferencedError: 'Promise is undefined' for verdor.js
Most helpful comment
Seeing the same issue with webpack v3.4.1 in IE11.
ReferencedError: 'Promise is undefined' for verdor.js