vue-currency-input: Including vue-currency-input in vue project breaks IE 11 & Edge

Hi,

First of all, thank you for providing this library.

I just found out that a Vue project created with @vue/cli that uses vue-currency-input breaks in Internet explorer 11 and in Microsoft Edge with the following error

"Expected identifier, string or number"

The way to reproduce the problem is simple.

create a new project with vue with the defaults. Follow the instructions in https://dm4t2.github.io/vue-currency-input/guide/ to add Vue Currency to the project, run the project with yarn serve and open the url with IE 11 or MS Edge.

This kind of errors is usually caused by a trailing comma somewhere, but wasn’t able to find one.

Best regards, Rodrigo

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 15 (7 by maintainers)

Commits related to this issue

feat: improve browser compatibility (#15, #109, #112) A polyfill for `Intl.NumberFormat.prototype.formatToParts()` is no longer required for older browsers (IE 11, Safari < 13) — committed to dm4t2/vue-currency-input by dm4t2 4 years ago

Most upvoted comments

Good news: In the next release (probably 1.19.0) the requirement for Intl.NumberFormat.prototype.formatToParts() will be dropped again.

dm4t2 on Jun 3, 2020

Release 1.19.0 is now available 🤤

dm4t2 on Jun 11, 2020

Good news: In the next release (probably 1.19.0) the requirement for Intl.NumberFormat.prototype.formatToParts() will be dropped again.

Please faster 😄 my users with safari 10 are indignant

nPaul on Jun 7, 2020

Hi, since 1.18.0 browser support for Intl.NumberFormat.prototype.formatToParts() is required or needs to be polyfilled.

Adding the following snippet to your main.js should work:

if (!Intl.NumberFormat.prototype.formatToParts) {
    Intl.NumberFormat = require('intl').NumberFormat;
    require('intl/locale-data/jsonp/<your locale>')
}

You can also use a version < 1.18.0 if you don’t need support Arabic/Persian numbers.

dm4t2 on Apr 22, 2020

Thanks for your suggestion. I will add it in the docs.

Good news: IE11 will be supported in the next release (1.6.0) 🎉

dm4t2 on Jun 20, 2019