Skip to content
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.

Intl is still not a valid substitute for currency-formatter imho #72

Open
fedeolto opened this issue Dec 28, 2018 · 1 comment
Open

Comments

@fedeolto
Copy link

Hello,
after reading the first lines of the project page, I started substituting currency-formatter usages in my project with Intl, but I'm afraid that the world is not ready for this.
Problems arised when I tried to use it-IT as a locale for some currencies: I use Docker and node 10.10.0-alpine doesn't ship with full-icu (and I find it more than correct, since hardly full-icu would be used) so I would need to install it.
As reported here
nodejs/node#19214
having full-icu working seems to increase the binary size of 14M and I can't find a way to install only the locales I want: reading Intl documentation on Nodejs page seems that the only option to have currency formatting managing locales different than os ones is to install full-icu
https://nodejs.org/api/intl.html

I'm unsure if adopting Intl instead of currency-formatter is a good option when build size matters.
Any opinion is more than welcomed

Last but not least: my aim is to have a certain symbol as decimal separator and a certain other one as thousands separator. I'm not interested in sticking to a particular locale

@edorivai
Copy link
Collaborator

Just a quick remark on

my aim is to have a certain symbol as decimal separator and a certain other one as thousands separator. I'm not interested in sticking to a particular locale

If this is all you need, you might want to take a look at accounting.js.

smirzaei added a commit that referenced this issue Feb 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants