How does it compare to normal "Gettext workflow"?<p>Currently I use i18next with custom functions, where I just write strings like _("car"), ngettext("window", "windows", number) in files.
I Can use translator comments, context and everything. (Like //TRANSLATORS: this is used in this way etc.)
<a href="https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html" rel="nofollow">https://www.gnu.org/software/gettext/manual/html_node/PO-Fil...</a>
Babel extracts all translatable strings to POT file. I Translate POT file to my wanted languages PO files with GUI tool of my choice. Then PO file is converted to json and used in translations with i18next library.
When New translations are added I just rerun Babel new translations are added, are retranslated if needed and converted to JSON.
I looked into a lot of JS libraries and extractors and these was the only one that supported Plurals, context, translator comments, etc.<p>I looked into Mozilla's L20 which seems nice. But there is no GUI translation editor. You have to find all translatable strings yourself etc. End it seems it's the same here.<p>One better things is that with FormatJS I wouldn't need moment.js for date localization.