💡 Factory functions are the cheat code for ergonomic TypeScript APIs

🌐 next-intl 4.5.8 is out! Improvements for useExtracted: → Handle multiple calls to useTranslations and useExtracted → Avoid conflict with existing useTranslations import → Append newline with .json formatter

All I want for Christmas is a stable release of next/root-params for @nextjs.org … 🎄🎁

🌐 next-intl 4.5.7 is out with a significant middleware performance improvement for apps that use a large number of locales!

⏳ Last chance today! It’s also a great way to support the development of next-intl! ❤️ And I guarantee you’ll learn something new. If not, you get a full refund—no questions asked.

🌐 [email protected] is out! Improvements for useExtracted: → Fixes message reset race condition → Stable, environment-agnostic key sorting → Preserves 3rd-party .po flags → Handle encoding in .po files → Updates po-parser to v1 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

The Black Friday discount is live — 40% off! Updated for Next.js 16, lifetime updates included, lowest price it’ll ever be.

Finally switched 🌐 learn.next-intl.dev from LS over to Polar and couldn't be happier. I thought about migrating to Stripe Managed Payments, but I didn't realize how low-level this is until I had a closer look. Polar feels like exactly the right kind of abstraction.

🌐 [email protected] is out, where Donny, the creator of SWC, rewrote the AST transformer for useExtracted in Rust! 🏆 ~45% faster processing time ✅ Support for source maps github.com/amannn/next-...

I've just open-sourced the .po parser I've implemented for this feature. Might be useful in case you want to build custom tooling around! It might also come in handy if you want to implement a custom .po formatter for useExtracted in the future. github.com/amannn/po-pa...

Can't say that it wasn't tempting to make it a "use extracted" directive instead, just for the fun of the controversy ⚔️

🌐 next-intl 4.5: useExtracted → For humans & AI → Next.js-first by design → Full Turbopack support → SWC-based parsing

While everyone is arguing about directives, I’ve just used “using” for the first time, and now I feel like a TypeScript god

Following up on my demo of cacheComponents + next-intl, I wrote a blog post reflecting on the problem's background and better explaining the solution! aurorascharff.no/posts/implem...

Q: Does cacheComponents in Next.js 16 work with next-intl? A: No, at least not yet. The tldr; is that we need next/root-params and support for it within 'use cache'. Everything in next-intl is already in place to use this though. A bit more here → github.com/amannn/next-...

🌐 next-intl 4.4 is out with support for Next.js 16! Release notes: github.com/amannn/next-...

I'm curious about the future of `dynamicParams = false` for Cache Components in Next.js. I've opened a discussion to have a conversation about this, please share your thoughts here → github.com/vercel/next....

I didn't exactly have "build rust tooling" on my bingo card for next-intl in 2025, but here we are

Such an incredibly helpful setting, makes me wonder if this should be the default … nextjs.org/docs/app/api...

📄 RFC: First-class message extraction in next-intl The more eyes we can get on it, the better the feature will be—please share your thoughts with me! github.com/amannn/next-...

🌐 learn.next-intl.dev is officially live! Learn how to build delightful, multilingual apps with Next.js—from the basics to advanced patterns, all through a real-world project. 🎥 10 chapters · 42 lessons · 5+ hours of 4K video 💻 All code, recaps & resources included

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!

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! 🚀

> Being Heard Isn’t Just About Speaking — It’s About Understanding A really beautiful piece by Adebesin Tolulope iamlope.medium.com/being-heard-...

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...

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 [email protected] to get rid of the warning! github.com/amannn/next-...

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

🌐 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...

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

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.

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

☃️

React Context as a provider in React 19 is 🔥!

🌐 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...

Announcing 🌐 learn.next-intl.dev! Have a look and be the first to hear about the launch early next year!

Me the other day: "I'd wish `beforeEach` in @vitest.dev worked like `useEffect`, where I can return a cleanup function along with my setup code." Turns out it actually supports this pattern, how cool is that! https://vitest.dev/api/#beforeeach

Another fun one: select! Practically, this means you get autocomplete for known values, but arbitrary strings that will match "other" are also supported.

🌐 [email protected] preview: GDPR compliance To comply with current regulations, these changes will be made: 1. Decrease locale cookie expiration to 5 hours 2. The locale cookie will now only be set when a user switches to a locale that doesn’t match the accept-language header

Many thanks to @anaclumos.bsky.social for sponsoring me on GitHub! ❤️ github.com/sponsors/ama...

The best part of the implementation is that the type of the argument is inferred based on how the argument is used in a message. E.g. a plain param doesn't accept a number, but requires that the `number` formatter is used 😌

🌐 [email protected] preview: Strictly-typed ICU args

Once you get used to strict types, there's really no going back. I had quite some fun the other day adopting this in a real-world app 😊

🌐 [email protected] preview: Strictly-typed locale By strictly typing your supported locales, APIs like useLocale() or <Link /> that either return or receive a locale will now require a precise value based on a string union, improving type safety across your app.

👀👀👀👀 :it's happening gif:

Had to learn this the hard way the other day 🙈

🥲

Is there a technical reason why 'use cache' can not be used on synchronous components in @nextjs.org?

@andarist.bsky.social Do you by chance have any background on whether github.com/microsoft/Ty... is a priority for the TypeScript team? It seems like quite a popular request.

🌐 next-intl@4 development is in full swing! After a year of feature development, this release mostly aims to tidy up the API surface to ensure the library remains lean—no surprises. One area of improvement is an overhauled API for registering strict types!