You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: exposing more ICU functionality or data? #13550
Looking over a pull request like jsdom/tr46#11, which pulls in lots of Unicode data tables, and comparing it to Node.js's WHATWG URL implementation which apparently is just able to delegate to ICU, I was struck with the question of why more ICU data and functionality isn't exposed directly to JS? That would allow us to implement tr46.js without pulling in such data tables, or possibly just eliminate it entirely.
I imagine some of this might be work for ECMA-402, although my understanding is they're still figuring out whether they want to take an ICU dependency. But in the meantime Node.js already has all this data in the binary, from what I understand... any thoughts on exposing it to JS?
This is something I have considered on a number of occasions and keep running into the same "small core" objections. We need to come up with good use cases to justify then I'll be happy to pursue
Activity
richardlau commentedon Jun 8, 2017
There is nodejs/node-eps#15
jasnell commentedon Jun 8, 2017
This is something I have considered on a number of occasions and keep running into the same "small core" objections. We need to come up with good use cases to justify then I'll be happy to pursue
jasnell commentedon Jun 8, 2017
In general, I'm all for it
domenic commentedon Jun 8, 2017
Ah, seems like a dupe of the EPS; will close to centralize discussion there.