feat: generate messages type

[BobbieGoede]

🔗 Linked issue

• Enable type checking from vue-i18n nuxt-modules/i18n#2591
• $t() autocomplete support nuxt-modules/i18n#1753
• feat!: type-safe messages intlify/vue-i18n#1649

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This is still very much a work in progress!

For message type inference we need to merge the messages provided by all Vue I18n configs and locale files (probably limited to default language or a configured 'master' locale for perf) and use the merged messages to generate the messages type.

The generation of these types is still incomplete, we may not be able to (properly) support async locale configs due to its reliance on the Nuxt context ($fetch, useRuntimeConfig, etc.), this is the case for both defineI18nLocale and defineI18nConfig.

Maybe we should consider having a clear split between 'static' locale configs and 'runtime' configs instead of allowing both in defineI18nLocale? This would make it possible to generate types for such locales and bundle/fetch remote translations at build time if users prefer to do so.

Code_2024-07-17_14-54-20.mp4

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[kazupon]

Maybe we should consider having a clear split between 'static' locale configs and 'runtime' configs instead of allowing both in defineLocaleConfig? This would make it possible to generate types for such locales and bundle/fetch remote translations at build time if users prefer to do so.

Yeah, it make sense!
By separating static and dynamic locales as defineStaticLocales and defineRuntimeLocales, We can clarify locales management!