Fix operations with fragments in the Webpack loader for IE 11

[rocwang]

Pull Request Labels

• feature
• blocking
• docs

/label bug

I was using version 2.9.2 with the Webpack loader. On IE 11, I saw the following error:

Fragment was XXX used, but not defined

It turns out that on line 133 of loader.js, we have var newRefs = new Set(opRefs); and IE 11 doesn't support "new Set(iterable)", so I rewrite it to add the members of opRefs to newRefs one by one using forEach, which resovles the issue.

[apollo-cla]

@rocwang: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

[gabrielpieta]

Hello,

I have the same problem in the Internet Explorer 11. My websiste uses fragments in many places and to corret the problems I need of this correction.

Are you planning to make this fix available in a version of lib that I can use with yarn ?

[FernandoBasso]

Facing the same problem. Any idea when, if ever, this pull request will be accepted?

[gabrielpieta]

@rocwang: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

Hello @rocwang you make this process ? I really need to make this fix available =S

[rocwang]

@gabrielpieta I've just done that.

[abernix]

This change seems reasonable enough to me. It is very true that IE11 does not allow constructor arguments.

[abernix]

Please try [email protected] and see if this is resolved.

[gabrielpieta]

Wooooow, thanks man, I go try and report here!

[gfx]

@abernix Can you update CHANGELOG.md and push the tag of v2.10.1?

[abernix]

Done and done. Thanks, @gfx.