Doesn't work with IE11 (ducks for cover)

[wmertens]

I am using this in an SPA and it's really great, but it turns out that the npm version uses class in the JS, so it's not ES5.

Would it be possible to provide the npm code as ES5 code? I don't know what the current best way to provide ES6 code is, but this is the only package that causes problems in the build for our IE users.

In the meantime I'll try some workaround like forcing a babel compilation of this package.

[ooflorent]

I don't understand, are you shipping tapable into your bundle? tapable is just an utility used within webpack and its loaders/plugins. Could you detail what you are trying to achieve?

[wmertens]

Yes, I'm using it client-side to have a pluggable framework. It works great for that…

…

On Tue, Mar 20, 2018 at 4:02 PM Florent Cailhol ***@***.***> wrote: I don't understand, are you shipping tapable into your bundle? tapable is just an utility used within webpack and its loaders/plugins. Could you detail what you are trying to achieve? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#50 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADWlo7VYIa14eMMeSJADQJKZ_w9UlINks5tgRoVgaJpZM4SEeRL> .

[ooflorent]

Since the library is targeting node 6+, I don't think we would transpile it. Your best option is to include it into your babel-loader (instead of exclude: /node_modules/).

[wmertens]

Yes, I'm whitelisting it now. Fair enough, thanks!