-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
intl: Will Intl.Segmenter need full ICU in Node.js even for the 'en' locale? #24039
Comments
cc @nodejs/v8 @nodejs/intl. |
I'm a fan of anything that forces us to ship full icu |
The answer from the implementers:
Well, this is a strong argument to ship full ICU by default. |
Our table is not correct anymore: |
/cc @srl295 |
As I mentioned in #21676, we should separate dev & test builds from release builds. /CC @nodejs/testing |
Is there anything to do at this time other than be aware that This Is Coming? |
Should this be closed for the time being? If not, what is the condition for closing? |
Maybe clarification if this is wontfix from the ICU team? |
@nodejs/intl Are we going to start shipping full icu? Or not? Or to be determined? |
So,for this case, I'd think we would just change the definition of 'small icu' to include the break iterator files. It's this line, to change So probably this issue should be closed with "no", or used to put the needed fix in once this v8 change lands. |
We're shipping full icu by default now so closing. |
See tc39/proposal-intl-segmenter#50
The text was updated successfully, but these errors were encountered: