regeneratorRuntime not loaded on Android User-Agent with coffeescript

[edemaine]

Consider the following simple example for client/main.coffee (demo repo):

words = ->
  yield 'hello'
  yield 'world'

for word from words()
  console.log word

In a Chrome browser (on Windows), this correctly logs "hello" and "world" to console. However, if I set my User-Agent to Mozilla/5.0 (Linux; Android 4.1.1; Nexus 7 Build/JRO03D) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.166 Safari/535.19 (the Android option in User-Agent Switcher for Chrome), I get the following error message:

main.coffee:1 Uncaught ReferenceError: regeneratorRuntime is not defined
    at main.coffee (main.coffee:1)
    at fileEvaluate (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:346)
    at Module.require (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:248)
    at require (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:268)
    at app.js?hash=a04d86c6ea798e9fbb7d554b6c22aa47dbdae283:67

It seems that in this combination, somehow Babel is getting engaged (old browser), yet its polyfill isn't included. (This is a minimal example of an error that occurred in a real app using an actual Android device -- but this reproduction seems to accurately depict the problem.)

On the other hand, if I do equivalent code in ECMAScript, everything works fine no matter the User-Agent (to test in the demo repo, just change meteor.mainModule.client from client/main.coffee to client/main.js):

function* words() {
  yield 'hello';
  yield 'world';
}

for (word of words()) {
  console.log(word);
}

I conclude that this is probably a bug in the coffeescript module.

[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.

[edemaine]

I just checked that this bug is not fixed in Meteor 1.8.2. (Demo repo has been updated accordingly.) Could you reopen the issue?

[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.

[edemaine]

I assume, but have not checked, that this still hasn't been fixed, so should not be closed.

[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.

[edemaine]

I can confirm it's still a bug in the latest Meteor 1.9. My poor Android users. 🙁

[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.

[edemaine]

I'm not aware of this being fixed yet. Would appreciate some attention, or some pointers on what I might investigate...

[edemaine]

The same issue arises on the SeaMonkey browser.

[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.

[edemaine]

Still an issue. 🙁

[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.

[edemaine]

This is still an important issue for me. @GeoffreyBooth as the maintainer of the coffeescript module, perhaps you could take a look?

[GeoffreyBooth]

This is still an important issue for me. @GeoffreyBooth as the maintainer of the coffeescript module, perhaps you could take a look?

I’m sorry, I don’t have time at the moment. I would think it’s something to do with the Babel compiler build plugin.

[StorytellerCZ]

I'll look into updating coffeescript for Meteor 2.5, but no promises.