Next.js: Promise not polyfilled correctly in IE11

Created on 13 Jun 2017  路  8Comments  路  Source: vercel/next.js

In IE11, Promise is not defined in app.js and causes errors every page load:

screen shot 2017-06-13 at 3 46 09 pm
screen shot 2017-06-13 at 3 46 28 pm

I don't think the global polyfill attempt here is working:

screen shot 2017-06-13 at 3 51 19 pm

p0

Most helpful comment

Seeing the same issue with webpack v3.4.1 in IE11.

ReferencedError: 'Promise is undefined' for verdor.js

All 8 comments

You can reproduce the problem using the with-custom-babel-config example with [email protected]. There is no issue using next@latest.

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

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rauchg picture rauchg  路  3Comments

havefive picture havefive  路  3Comments

sospedra picture sospedra  路  3Comments

lixiaoyan picture lixiaoyan  路  3Comments

jesselee34 picture jesselee34  路  3Comments