Links not working in IE11 production build
See original GitHub issueI see the following error in the console:
Unable to get property 'push' of undefined or null reference
production-app.js (87,7)
That line corresponds with the following line of code:
window.___history.push(pathname)
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
React production build not working with IE 11 - Stack Overflow
When I am creating production build using "npm run build" and running it using "node server.js" it works in Chrome but in IE...
Read more >Internet Explorer 11 is not opening links - Microsoft Community
An installed add-on is a possible cause of the issue you're experiencing with opening hyperlinks in Internet Explorer. We advise running the app ......
Read more >IE11 error when build with production option #14777 - GitHub
When I build the project in production mode using following command: ... there is an error in IE11 console and the app do...
Read more >Handling common JavaScript problems - MDN Web Docs
For example, in bad-for-loop.html (see source code), we loop through 10 iterations using a variable defined with var , each time creating a ......
Read more >Angular and Internet Explorer - InDepth.Dev
Notice that now, when you run the build, it is producing the ES5 bundles: <>Copy. $\ie-test> ... How To Fix Your Angular App...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I don’t think it automatically needs polyfill as long as it is clear how to customize the build process to have babel do that.
Another example - I am trying to use
async
andawait
in agatsby-node.js
file butgatsby develop
blows up.If it was a standard vanilla project I would just throw in a .babelrc with the correct settings and configure webpack and be good to go. With gatsby, I am not sure how to actually set it up.
No we don’t automatically polyfill old APIs. Perhaps we should? /cc @jquense thoughts?