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
After the proper installation, the unicode files are there and can be used with node-stringprep. @lloydwatkin is also working on a fallback solution. But be aware, this mean it work, but unicode string conversion is not as safe as before.
@lloydwatkin and @dodo is it possible to include the unicode files from icu in our project and compile them with node-stringprep this would eliminate the external dependencies.
Activity
chris-rock commentedon Jan 13, 2014
You do not meet the precondition. Please try:
After the proper installation, the unicode files are there and can be used with node-stringprep. @lloydwatkin is also working on a fallback solution. But be aware, this mean it work, but unicode string conversion is not as safe as before.
chris-rock commentedon Jan 13, 2014
@lloydwatkin and @dodo is it possible to include the unicode files from icu in our project and compile them with
node-stringprepthis would eliminate the external dependencies.chris-rock commentedon Jan 13, 2014
#37
michaeldauria commentedon Jan 13, 2014
I used
brew link icu4c --forcebut that didn't do the trick, the above does. Also, for you Boxen folks out there:chris-rock commentedon Jan 13, 2014
+1 thanks for the solution with boxen.
lloydwatkin commentedon Jan 13, 2014
Thanks for boxen instructions, have added to wiki.
dodo commentedon Jan 14, 2014
@lloydwatkin in which wiki did you put the instructions? it seems i'm to dumb to find a link :P
lloydwatkin commentedon Jan 14, 2014
Too much wiki editing yesterday! Readme.md, might be under
node-stringprep-icudodo commentedon Jan 14, 2014
yep, thx … found it.