Vite support for createMessagesDeclaration (use-intl)

[mhornbacher]

use-intl is a highly underrated library for localization as unlike others it actively manages Timezone localization quietly with any rendered date.

It would be awesome to expand its type-safe nature to other solutions such as Tanstack Start or Remix by creating a plugin to generate the .d.ts file in that pipeline as well!

Do we think that this is outside of the scope of what use-intl is designed to do?

[amannn]

Thanks for the question, and for seeing potential in use-intl! I think eventually it could be something interesting to do, there's currently a very loose issue on this here: #1863.

Realistically, it's just quite a bit further down the road though. There are still some features and improvements that I'd like to land for next-intl to get it to a place where I consider it to be mostly feature complete (mostly #2087, #962 and #1).

I think it could be cool to add 1st party support for other React-based frameworks, but for the time being it's just helpful to double down on a single framework since, to be quite honest, it's already quite a bit of work of really nailing that in my opinion. I think that should also help to really know what works and take all the learnings to other frameworks.

As for createMessagesDeclaration, it's actually only a few lines that, if relevant, I think you could easily add for Vite or similar: createMessagesDeclaration.tsx. Ideally, I'd like to get rid of it anyway (related to microsoft/TypeScript#32063), therefore I'm holding back a bit with adding more API in regard to this.

Are you using use-intl with any other frameworks? Someone just wrote a lengthy blog article about usage in TanStack recently: #1863 (comment)