-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intl.RelativeTimeFormat and Intl.ListFormat don't work on languages other than English on node 12.10.0 #29525
Comments
By default node only ships with a small subset of internationalization data. We are planning to increase the internationalization data available in future releases. You can watch #29522 for more information on that. On current versions of node, https://nodejs.org/api/intl.html has information on how to build node with full intl data or load it at runtime. |
@devsnek thanks for the clarification. Closing it! |
Intro to my problem
I looked at the video from Google IO 2019 that talked about the latest features in javascript, and there was a part on improvement on
Intl
API and I wanted to try it out myself by using the latest version of node (12.10.0
at this time of writing):and I confirmed again that the new features for
Intl
work on node v.12+ from these articles:from v8's blog as well.
These are the things I tested on my laptop (mac OS) and also on my AWS EC2 Ubuntu instance (because I wanted to be as objective as possible):
Problem description
Mac OS
Ubuntu 18.04
Chrome 76 (on my mac)
FYI, I used the code snippets from Google IO 2019 to avoid writing stupid things by mistake. Yeap. As you can see, Chrome 76 perfectly outputs what's expected, while node repl on both operating systems did not work as expected. They only give outputs in English, which I think is a default fallback option.
If this is real, I think it is a huge error, so I am still in a big doubt thinking if node v.12+ really supports these features. Is this really a bug?!??
The text was updated successfully, but these errors were encountered: