Skip to content
This repository was archived by the owner on Feb 29, 2020. It is now read-only.

Discoverability/Modularity of ICU Data File #11

Closed
jasnell opened this issue Aug 11, 2015 · 4 comments
Closed

Discoverability/Modularity of ICU Data File #11

jasnell opened this issue Aug 11, 2015 · 4 comments
Assignees

Comments

@jasnell
Copy link
Member

jasnell commented Aug 11, 2015

One of the key issues around the introduction of Intl support into node has been the bundling of the ICU data file and the use of the command line switch. One of the solutions discussed has been to allow Node to automatically discover the data file location and to use modules as a way of installing / customizing the data file. I have been investigating several options on this and will be using this issue to track the progress.

@srl295
Copy link
Member

srl295 commented Sep 28, 2015

from some discussions today:

  • have a generic npm package named something like icu4c-data
  • that package has a postinstall step ala node-sass which in turn:
    • does an npm install icu4c-data-${ICUVER}${ENDIANNESS}
    • .. but copies the data file 'up' into ../node_modules/icu4c-data (flat path)
    • emits "Hey, to use this run node --icu-data=node_modules/icu4c-data
    • ... until node can discover that data file by itself (#????)
  • node installer might offer to do an 'npm install -g icu4c-data` on behalf of the user.

@srl295
Copy link
Member

srl295 commented Oct 24, 2015

issue: nodejs/node#3460

@srl295
Copy link
Member

srl295 commented Feb 2, 2016

^ PoC up at the above issue

@Trott
Copy link
Member

Trott commented Dec 11, 2017

Closing due to inactivity. Feel free to pick this up again in nodejs/node#3460 or any other nodejs repo that seems appropraite. This one will probably be read-only soon.

@Trott Trott closed this as completed Dec 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants