SCRIPT1014: Invalid character error on IE

[TomiTakussaari]

Open https://www.gatsbyjs.org/ or https://op-developer.fi on IE10 or IE11, and you get this kind of error to console, with unfortunate effect of disabling rest of javascript on site:

(I am using Windows 10 & IE11 on Browserstack)

https://op-developer.fi is using Gatsby 1.6.6, but same problem seems to be with Gatsby 1.8.11 too.
Pre 1.0 versions of Gatsby did seem to work though.

Looking at IE debug tools, it kind of looks like it happens because of backtick usage in loaders/gatsby-module-loader/patch.js, but would have though that Babel would convert those.

Also some Gatsby sites seem to work fine, or atleast better, on IE, so not really sure what is going on.

Should Gatsby even still work with IE's ?

[TomiTakussaari]

Funny thing is, if I test with IE11 locally, running gatsby develop, everything works just fine and there are no errors.

[TomiTakussaari]

After replacing backticks on patch.js with double quotes ("), I got different error:

I guess that's enough for today then, no idea how that could work in other browsers, but fail on IE.

[TomiTakussaari]

Reverting back to Gatsby 1.5.0 fixed this issue for me.

[KyleAMathews]

Lemme know if the latest release with #1901 fixes things!

[TomiTakussaari]

#1901 fixed the original error, and for example https://www.gatsbyjs.org/ now seems to work fine on IE, thanks!

But on my site i now get this same error I reported in #1839 (comment).

Apparently it has something to do with my code, because it does not happen universally, but I have no idea what could cause it only on IE & IOS7 Safari.

Gatsby 1.5.0 is free of this issue as well.

[KyleAMathews]

hey progress!

On your error — best way forward is if you can recreate the error in a small reproduction site. Copy your site and try stripping away everything until you have the smallest site possible that still creates the bug. I can look at it then.

[TomiTakussaari]

Ok, so apparently this latest "Unable to get property pathname of undefined or null reference" was because babel-polyfill was imported in gatsby-browser.js, and not in gatsby-node.js/modifyWebpackConfig.

So importing it via gatsby-browser.js worked for some reason until gatsby 1.5, but with later versions it needs to be added via modifyWebpack.

So I guess this is solved by that.