github.com/amannn/next-...

If you already gave it a shot, please share your feedback here:

github.com/amannn/next-...

Before:
- Think of a message ID (This is often hard!)
- Define your message text
- reference the message ID

After:
- Tag your string as translatable

Btw. I saw your GitHub issue, will reply a bit later on today!

Nice! How did you set up the migration? Are you using different folders for useExtracted and useTranslations messages?

There's btw. another release scheduled for this week with a few fixes for useExtracted: github.com/amannn/next-... — just as a heads-up!

Ok nice! Hope it stays like that, bundling behavior of Next.js can be peculiar…

But you'd still load your server implementation like getItemServer on the client side, right? If it's doable for you, it might be worth considering if another API requires less magic …

So it's kind of a factory function that returns functions for both the server and client? You could check with the new bundle analyzer (next experimental-analyze --serve) on the latest canary if everything tree-shakes as expected.

Ah yep, got it! Hmm, to be honest—not entirely sure. It kind of rings a bell this pattern, I think I saw it in some userland code in a GitHub issue. next-intl doesn't do it though and I don't really have first-hand experience with it.

Hey! Hmm, good question. Why did you move it to a dynamic import in the first place?

It’s just really helpful to focus on a single framework until we get there. And from there, eventually I‘d like to take all the learnings and make them available to other React frameworks. It will take time.

I mean the bigger topic is that it would be pretty cool if next-intl would have first-class support for other frameworks. I think eventually we’ll get there, but it’s pretty far down the road. I hope that next year, next-intl will somewhat reach „feature completion“, at least more or less.

If that’s an option for you, that might work. But: Things are still changing, if you can wait a bit, maybe this will be easier soon. I‘m currently working with Donny, the creator of SWC, to move all the AST modification to an SWC plugin. I guess using that somehow in a Vite app should be possible.

What will be missing for you is the part where inline messages are swapped out for keys. So useExtracted in theory already works in Vite, but it will always use the message you've defined inline (typically your source locale).

But it's something further down the road, I'd like to get more confidence that this works well for Next.js first.

For now, useExtracted is Next.js-only. But the Next.js-specific integration point is a Turbopack loader which is literally just this small file here: github.com/amannn/next-.... So the feature was certainly implemented to be useful for other bundlers like Vite as well.

Got it! Let me know if it works well for you when you get a chance to try it!

Did you have a chance to try it yet? :)