Open TBG-FR opened 2 years ago
Hey! Sorry for the latence. But, wdym by "I package it". Have you an repo for this code to test every things.
Hey! Sorry for the latence. But, wdym by "I package it". Have you an repo for this code to test every things.
No worries 😉 I detailed every step here https://github.com/vercel/pkg/issues/1731
Hey! Sorry for the latence. But, wdym by "I package it". Have you an repo for this code to test every things.
No worries 😉 I detailed every step here https://github.com/vercel/pkg/issues/1731
This isn't a packagable package. It's a loading hack. In short: Don't prepackage it... more on this later.
You could help us split full icu into a Helper library maybe ?
Hello there !
Issue summary
I can't get an environment in
small-icu
without pain, and without a such environment, I can't get the files needed to switch tofull-icu
in another appProposal
Could we have an option to still get
icudtxxy.dat
files downloaded intonode-modules/full-icu
, even if we are not insmall-icu
and it will probably be useless ?Details
I'm facing issues with
pkg
, that allows to build binaries. It looks like that pkg is built withsmall-icu
, and that causes issues in my app. However, to give the right icu files (i.e.icudt70l.dat
), I need to get them, andfull-icu
won't let me, because the original environment/node isn't in small-icu (Note: Your node was not compiled with the ‘small-icu’ case, so the ICU data is not customizable through this script. Exitting.)However, since Node is now built in
full-icu
, I can't get asmall-icu
, I spent many hours trying, without success 🤯 Theicu4c
version I need isn't available onnpm
, and I don't know what to do with Github releases to get the.dat
files... And full-icu seems to be my savior here, it knows how to handle all of these !Here's a basic example (
index.js
)If I run it inside a node docker (my usual dev environment), I get
But once I package it, I get
Many thanks in advance ! 🙏