Skip to content
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

[Discussion] intl-universal vs react-intl-universal #120

Open
DongShi opened this issue Sep 6, 2019 · 1 comment
Open

[Discussion] intl-universal vs react-intl-universal #120

DongShi opened this issue Sep 6, 2019 · 1 comment

Comments

@DongShi
Copy link

DongShi commented Sep 6, 2019

Hey there:
You guys have done a good job, to push i18n work out of viewer, into a self-contained bundle compared to react-intl.

But apparently, this lib still depends on reactjs, (you guys provide getHTML method, etc).
Why not make it a standalone and library agnostic package, so other library users can also benefit from your work?

Or maybe you could provide some build option to just build the "core" functionality for i18n, with no reactjs related part?

@cwtuan
Copy link
Collaborator

cwtuan commented Sep 9, 2019

That's good idea.
We will take it into consideration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants