Jan

Screenshot of the course project

A sneak peek at what to expect from 🌐 learn.next-intl.dev:

→ No oversimplified examples
→ Built around a real-world project
→ Holistically transitioned to fully internationalized

Full course reveal coming next week!

Screenshot of the course platform

I thought this course would take 2-3 months.
It took eight.

But now, learn.next-intl.dev is almost ready: Learn how to build delightful, multilingual apps with Next.js — launching next week! 🚀

I‘d be really curious about more real world use cases for the currentState argument in the docs. I usually end up ignoring it 🤷‍♂️

Being Heard Isn’t Just About Speaking — It’s About Understanding Great apps don’t just talk — they listen. Learn how i18n with next-intl helps your Next.js app understand users in their own language.

> Being Heard Isn’t Just About Speaking — It’s About Understanding

A really beautiful piece by Adebesin Tolulope

iamlope.medium.com/being-heard-...

These are things you could do in RSC too, right? It somehow is a petty though that Next.js doesn’t allow fully cached responses if you read search params.

Is it by chance also planned to forward logs from Server Actions to a browser that has called them? Not sure if that somehow fits into the protocol, but it would be nice to simply have all server logs available in the browser :)

Really, really exciting—thanks for sharing all your research with the community! ❤️

TIL about i18n-check!

This CLI helps you validate against:

1. Missing translations in target locales
2. Inconsistent usage of ICU arguments
3. Unused translations with next-intl (exp.)

Learn more → next-intl.dev/docs/workflo...

Release v4.0.3 · amannn/next-intl 4.0.3 (2025-04-22) Bug Fixes Support stable Turbopack config in Next.js 15.3 (#1850) (30ec8e0), closes #1838 – by @amannn

If you've already upgraded to Next.js 15.3 and you saw a deprecation warning about Turbopack config with next-intl, you can now upgrade to next-intl@4.0.3 to get rid of the warning!

github.com/amannn/next-...

next-intl ultimately requires a JS object with properties as keys and labels as strings. But I guess you could easily transform a .po file, either with a CLI or even at runtime (with caching if you like)

In case you want to set up a translation program as well, the Ethereum team shares their playbook on how to create one.

→ ethereum.org/en/contribut...

They've also set up a translation program to help the community contribute translations with Crowdin. So far, 6,900+ translators have joined the effort! 🤝

→ ethereum.org/en/contribut...

TIL that the Ethereum website uses next-intl to localize its content to 69 languages—how cool is that! 🤯

→ ethereum.org

Glad to hear you like it! Let me know how it goes with v4! 🙌

next-intl 4.0 – Internationalization (i18n) for Next.js Internationalization (i18n) for Next.js

🌐 next-intl 4.0

→ Revamped augmented types
→ Strictly-typed locale
→ Strictly-typed ICU arguments
→ GDPR compliance
→ Modernized build output
→ Preparation for PPR, dynamicIO & rootParams
→ … and more!

next-intl.dev/blog/next-in...

Hey Oliver, thanks for reaching out! I just watched your talk, intlc looks really, really cool 👏 Also many of the points you mention in the talk sound familiar to me! Let me reach out via DM, I might hit the post character limit here 😄

Last call to provide feedback if you haven't already! 👀

Middleware size is affected by messages in Next.js 15 · Issue #1669 · amannn/next-intl Description I got an error when I deploy to Vercel. The error is: The Edge Function "src/middleware" size is 1.65 MB and your plan size limit is 1 MB. All translations are packaged into a middlewar...

As a side note, Next.js 15 currently has a tree-shaking issue which can cause your messages to leak into the middleware bundle. The Next.js team has confirmed the issue.

More context & workaround: github.com/amannn/next-...

fix: Merge `link` header from middleware with the ones from React by amannn · Pull Request #73431 · vercel/next.js Fixes #69000

For context: github.com/vercel/next....

Also in this release: Link headers that are returned by a middleware are now merged with other ones that Next.js might set for fonts & images.

If you've been waiting with upgrading to Next.js 15 due to this, now's the time! The next-intl docs have now been updated to Next.js 15 as well.

Really cool!

Super nice! 👏 Was the migration straightforward?

Who has already tried the beta? Anything you've encountered?

Thanks mate! Was really incredible light yesterday morning with the mist and all ✨

Me this morning after a ski tour up a mountain, about to ride down

☃️

Code sample showing how a React Context can be used as a provider.

React Context as a provider in React 19 is 🔥!

I’m really excited about that one too. 😌 Let me know how it works for you in case you give it a shot!

next-intl 4.0 beta – Internationalization (i18n) for Next.js Internationalization (i18n) for Next.js

🌐 next-intl 4.0 beta

→ Revamped augmented types
→ Strictly-typed locale
→ Strictly-typed ICU arguments
→ GDPR compliance
→ Modernized build ouput
→ Preparation for PPR, dynamicIO & rootParams

next-intl.dev/blog/next-in...

Guter Artikel, danke für die Tipps! Muss mir Warp mal anschauen, bin noch einer der vermutlich letzten die bei Hyper hängengeblieben sind …

Way too kind of you, thanks Matthias! 😊😊