Profile avatar
amann.work
Maintainer of 🌐 https://next-intl.dev · Guest lecturer for React Web Applications at FHV · Partner for User Interface Engineering @jamannnnnn on X
106 posts 182 followers 341 following
Regular Contributor
Active Commenter

> 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