meteor 1.5-rc.10 on Internet Explorer 11: can't redefine non-configurable property __esModule

[macrozone]

I have updated an app to 1.5-rc.10 and i get a client error on internet explorer:

SCRIPT5078: Die nicht konfigurierbare Eigenschaft "__esModule" kann nicht neu definiert werden

(should be in english: can't redefine non-configurable property __esModule)

it happens on this line:

import { useDeps, composeAll, composeWithTracker, compose } from 'mantra-core';

[macrozone]

ok, happens when .babelrc contains the preset "es2015" or "env"

By the way, what are the recomended .babelrc settings for meteor?

[benjamn]

I believe this will be fixed once 1.5-rc.11 is available (currently publishing).

By the way, what are the recomended .babelrc settings for meteor?

Our hope is that you shouldn't need a .babelrc file at all, but I would specifically caution you that babel-preset-es2015 and babel-preset-env are likely to overlap significantly with babel-preset-meteor, which is always included.

[macrozone]

@benjamn thx, will check if it works.

I think my other reported issues are all because of babel-preset-es2015. I will verify that

edit: I need the 2015 preset for react-storybooks and storyshots

[benjamn]

No rush, but please close this issue whenever you can confirm it's fixed in Meteor 1.5.

[jonasblumer]

@benjamn I'm having the same issue (with meteor 1.5, same error message in ie11)
also doesn't work when using babel-preset-meteor. i get the following error when running storyshots

=> Loading custom .babelrc evalmachine.<anonymous>:1 (function (exports, require, module, __filename, __dirname) { import { configure, setAddon, addDecorator } from '@kadira/storybook'; ^^^^^^ SyntaxError: Unexpected token import

[pozylon]

Hi there, same here. Argh IE11 !!!

[macrozone]

here is the fix when using storybook:

do not use es2015 for root .babelrc as @benjamn stated.

Add an additional .babelrc inside .storybook folder:

{
  "extends": "../.babelrc",
  "presets": ["es2015", "stage-2", "react"]
}

[ffxsam]

I believe this is what's causing my app to not work at all on IE11. It's making Flow Router choke, and none of my routes work. This is with Meteor 1.5.

[ffxsam]

Disregard. Rolled back to Meteor 1.4.x, and I'm still getting the "There is no route for the path: /xyz/abc" error in IE11. I don't get any other details, so this one seems pretty tough to debug. 😢

[skirunman]

Can this be closed?

[hwillson]

Sounds like this has been resolved. Thanks all!