-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packaging for JavaScript #1175
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Discussion:
|
@sffc my interest in icu4x comes from it being a possibility for implementing intl/temporal in engine262, so within the bounds of that (which i haven't touched since november, so i'll need to regain some context there) i can try to give feedback and small fixes but i don't have the bandwidth to spearhead this. |
As a reminder of the impact of this issue, nearly 2/3 of developers use npm, according to the 2022 Stack Overflow Developer Survey: https://survey.stackoverflow.co/2022/#section-most-popular-technologies-other-tools |
This issue tracks tasks that need to be completed for ICU4X to be easily included by JavaScript clients.
For people landing on this thread for the first time: Long story short, ICU4X is a new modular i18n library written in Rust. In order to deploy it on the Web (and possibly in Node.js), we have invested time in WebAssembly bindings that enable JavaScript clients to use ICU4X as if it were a native JavaScript library. The next step, where we would like to start engaging more with folks like you, is how to package up all the work we've done into a polished, modular package that can be easily integrated into all types of JavaScript apps.
Some open questions include:
Additional sub-tasks:
The text was updated successfully, but these errors were encountered: