Feature request: exposing more ICU functionality or data?

[domenic]

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?

/cc @littledan @TimothyGu @jasnell @Sebmaster @srl295

[richardlau]

There is nodejs/node-eps#15

[jasnell]

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]

In general, I'm all for it

[domenic]

Ah, seems like a dupe of the EPS; will close to centralize discussion there.