-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IE11: Symbol is undefined #26
Comments
hey, thanks for reporting this. I don't want to include babel polyfill as a direct dependency because I think that decision should be left to the library consumers. It would be good to add a note about use of |
@phpnode So that's the thing. I'm adding |
I think that's what's happening. Here's a look at the transpiled output of my entry file: Object.defineProperty(exports, "__esModule", {
value: true
});
var _flowRuntime = require("flow-runtime");
var _flowRuntime2 = _interopRequireDefault(_flowRuntime);
require("babel-polyfill");
var _domainsConfig = require("./domains.config.js");
var domains = _interopRequireWildcard(_domainsConfig);
// etc
|
ok, a couple of work arounds for now:
/* @flow */
/* @flow-runtime ignore */
import 'babel-polyfill';
import './entryPoint'; or:
/* @flow */
import 'babel-polyfill';
import t from 'flow-runtime'; // the babel plugin will detect this and not import another copy.
// rest of your code goes here The problem is that we're attaching the import to |
@doctyper did the work around work for you out of interest? |
I'm not sure. It's still throwing an error, but I think it's because of the use of another unsupported API (generators). I think there's a larger need for a polyfilled, browser-friendly version of this plugin. |
Fixed import ordering and added rollup and browser / commonjs / es2015 builds in v0.2.0 |
Hi, great tool! I get this error when running flow-runtime on IE11:
Perhaps adding
babel-polyfill
as a dependency would fix it?The text was updated successfully, but these errors were encountered: