meteorBabelHelpers is Undefined in the Cordova Bundle (iOS) in releases > 1.8.1

[d0liver]

I'm attempting to build for iOS (with Cordova on macOS) on any Meteor release above 1.8.1. Running the app in the iOS simulator produces a meteorBabelHelpers is undefined error coming from multiple Meteor packages using coffeescript like https://github.com/softwarerero/meteor-accounts-t9n and https://github.com/arillo/meteor-flow-router-helpers. I did some digging and it looks like meteorBabelHelpers was supposed to be exposed to node_modules in the legacy bundle here: #10596.

I'd guess that what's happening is that these are old packages that are now compiling with coffeescript@2.x and leaking out newer syntax to Babel (since coffeescript 2.x doesn't attempt to polyfill newer syntaxes), but meteorBabelHelpers isn't available in the legacy environment for Meteor packages.

[hexsprite]

Hey, I had this same problem. I ended up forking the packages and adding this at the top of each .coffee file:

meteorBabelHelpers = Package.modules.meteorBabelHelpers

which solved the issue for me. I didn't have that many coffeescript packages.

I had filed some issues about this but there wasn't much interest in fixing it ;)

[d0liver]

@hexsprite Thanks very much. I was able to get this working doing what you suggested. I'm going to leave this open though, because I think that this effectively breaks compatibility with CoffeeScript for users unless they're willing to maintain their own forks of integral packages.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[xet7]

I do also get this error on IE11

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed it has not had recent activity.

[filipenevola]

Is the workaround suggested by @hexsprite enough?

[xet7]

@filipenevola

No, legacy bundle and browser detection code is broken so that's why Meteor/Wekan does not currently work in IE11 at all. Those dependencies should be updated to upstream, or alternative working dependencies proposed.

[filipenevola]

Sorry @xet7, I'm confused here, are they the same issue?

Our devel branch (1.11.1) is passing on IE11 in our regressions tests running on BrowserStack as you can see here https://app.circleci.com/pipelines/github/meteor/meteor/450/workflows/bbcf6bcc-ccac-4569-8206-527311c70f20/jobs/49616

Is our BrowserStack test reporting the incorrect result? Or is it something else like in this case #11163?

[xet7]

@filipenevola

After I updated Wekan to meteor devel at wekan/wekan@9087bd6 , I still see undefined errors on IE at https://friend.wekan.team (test server running meteor devel, you can register account) like this:

Those errors are not visible at Firefox and MS Legacy Edge.

Maybe it's some dependency?

[StorytellerCZ]

Just to confirm, this only issue in IE11?