Question: migration path from `react-intl` to `js-lingui`?
See original GitHub issueHas there been any documented approach (or tooling) around ways to migrate an existing code-base from react-intl
translations to js-lingui
translations?
I have a rather large codebase that was originally built around react-intl
but I’d like to change it to use js-lingui
everywhere… but not finding much direction on tackling this project.
Any suggestions?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Comparison with react-intl — LinguiJS documentation
LinguiJS is in many ways very similar: both libraries use the same syntax for messages (ICU MessageFormat) and they also have very similar...
Read more >lingui/js-lingui - Gitter
At the moment I'm using react-intl , but I'm looking into migrating to lingui . Anyway, my question is somewhat unrelated to the...
Read more >Tutorial - Internationalization of React Native apps - LinguiJS
Here we will cover parts that are relevant for React Native and hopefully answer all questions you may have. Note. The latest version...
Read more >Overview | Format.JS
This way when using the "main" module in Node all locale data is loaded, but ignored when bundled for the browser. An ES6...
Read more >Seemless, simple translation for you reactjs App using fast ...
You told us why you did not choose react-intl or react-i18next, ... and pondering about migrating to jsLingui since my project is at...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, you’re correct. If you use
i18nMark
, you need to feed the variable toi18n._
.i18n.t
could be used directly like:I’m closing this issue as it becomes a bit obsolete. If anyone recentl migrated from react-into to LinguiJS, feel free to send a PR with migration guide.