V4.0 Roadmap

[ryandrewjohnson]

Work has officially started on v4.0.

Below is a list of the proposed work, and features. If you have any interest in contributing the work is being done in the 4.0-dev branch.

✅ Update to latest React, and leverage hooks where possible
✅ Update dependencies
✅ Remove Flow and replace with TypeScript
✅ Replace webpack with rollup
✅ Update TypeScript definitions
⃞ Update demo [In Progress]
✅Make performance improvements
⃞ Look at having translations being attached to components (allow for removing translations when component unmounts)
⃞ Investigate any performance gains by using lodash.get vs current implementation using flatten
⃞ Add custom useTranslate() hook to API
✅Include #134
⃞ Rethink API footprint, and reference #139
⃞ Remove anything marked as deprecated
⃞ Update docs #141 #142

[ryandrewjohnson]

I'm going to be busy for the next while, so if anyone wants to help out with this please feel free to reach out.

[erwanriou]

I would think about any kind of similar system of management such as locize.io or equivalent, to connect the json translate files to a better system to update.
I build all my system with your library, and could even connect advanced translated routing system with it. Was quite amazing. Now i face the issue to make this easier to translate by non-developer peoples.

If by anycase you want to go in this direction, that would be a great idea.

[ryandrewjohnson]

@erwanriou thanks for this great suggestion. I will keep this in mind ... if I can ever get the time to work on v4 🤞

[dhwang]

On the theme of making it easier to non developers, Can this support PO file?

https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Web_Localizability/Localization_formats#gettext_(.po)