IE11 does not load any sandbox, user is greeted only with a blank page. Console error shows SCRIPT1005: Expected '('. Seems to be related to generator functions not being transpiled since this is the problem spot:

I was attempting to use codesandbox to test the IE11 compatibility of another library but ended up finding out that codesandbox isn't compatible either.
| Software | Name/Version|
| ---------------- | ---------- |
| 小odesandbox | PROD-1539347246-8f1f711
| Browser | IE11
| Operating System | Windows 10
I got the same issues in react projects on Windows 10/IE11, too.
IE11 Development Tools > Console:
SCRIPT1005: Expected '('
common.7273bfe3.chink.js (1,1142370)
Click on error line brings me to the debugger. It says:
Opening webpack:///home/circleci/codesandbox-client/node_modules/yallist/iterator.js
'use strict'
var Yallist = require('./yallist.js')
Yallist.prototype[Symbol.iterator] = function* () {
for (let walker = this.head; walker; walker = walker.next) {
yield walker.value
}
}
Might be possible its because the generator function (function* (){}) isn't supported by Internet Explorer. function*#Browser_compatibility
I am getting a similar issue trying to load a project with react 16.6 https://codesandbox.io/embed/w0573w2owk
I confirm. I can't use codesandbox to demonstrate issue on IE 11:

Its still an actual issue
Issue is still present even on standard, unforked sandboxes:
vanilla:
https://vanilla.codesandbox.io/
react:
https://new.codesandbox.io/
Debug output in IE11 on Windows 7:
HTML1300: Navigation wurde ausgef眉hrt.
Datei: vanilla.codesandbox.io
DOM7011: Der Code auf dieser Seite hat die Zwischenspeicherung f眉r das Vor- und Zur眉cknavigieren deaktiviert. Weitere Informationen dazu finden Sie unter: http://go.microsoft.com/fwlink/?LinkID=291337
Datei: new.codesandbox.io
SCRIPT1005: '(' erwartet
Datei: common-sandbox.ee8433bc.chunk.js, Zeile: 15, Spalte: 345270
SCRIPT1006: ')' erwartet
Datei: vendors~sandbox.b6b2495b.chunk.js, Zeile: 1, Spalte: 641
SCRIPT1002: Syntaxfehler
Datei: default~app~embed~sandbox.7010b461.chunk.js, Zeile: 1, Spalte: 7705
SCRIPT1010: Bezeichner erwartet
Datei: sandbox.f9b30660.js, Zeile: 1, Spalte: 30243
SCRIPT0: Ung眉ltiges Zeichen
Datei: babel-transpiler.134690e0.worker.js, Zeile: 14, Spalte: 1
SCRIPT0: Ung眉ltiges Zeichen
Datei: babel-transpiler.134690e0.worker.js, Zeile: 14, Spalte: 1
SCRIPT0: Ung眉ltiges Zeichen
Datei: babel-transpiler.134690e0.worker.js, Zeile: 14, Spalte: 1
Thank you @lbogdan! Hopefully the fixes get pushed to production soon.
Like @christianalfoni said in #2176:
With Overmind we do not really support IE11 as it is based on proxies.
So this one can be closed I guess? 馃
In the long term, we do want to support IE11 as well, but it's broken today.
Leaving this open as a bug, so that we can keep track of it.
In the long term, I fear IE 11 will be gone. I believe that the longer the issue is open, the less valuable it will be. What about closing it instead?
In the long term, I fear IE 11 will be gone
That's true 馃槃
We need to decide the usage threshold below which we can confidently say we don't support it. Today, it's still a sizeable number
I have seen a couple of people exploring IE 11 issues on Material-UI raising the problem about the inability to reproduce. If you are reading this message, you can try StackBlitz, for instance: (https://stackblitz.com/edit/react-7gp9j2)
Same for vanilla JS projects:
IDE: https://codesandbox.io/s/quizzical-darkness-x0i9b
App: https://x0i9b.csb.app/
SCRIPT1002: Syntax error
sandbox-startup.1db63978b.js (1,15784)
SCRIPT1010: Expected identifier
vendors~sandbox.be5921889.chunk.js (1,8878)
SCRIPT1002: Syntax error
default~app~embed~sandbox.ad29a3285.chunk.js (1,16090)
SCRIPT1010: Expected identifier
sandbox.f2591e6b5.js (1,24812)v
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.
bump
This issue has automatically been marked stale because there has been no activity in a while. Please leave a comment if the issue has not been resolved, or if it is not stale for any other reason. After 2 weeks, this issue will automatically be closed, unless a comment is made or the stale label is removed.
Bump
Most helpful comment
In the long term, I fear IE 11 will be gone. I believe that the longer the issue is open, the less valuable it will be. What about closing it instead?