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
93 posts 160 followers 325 following
Regular Contributor
Active Commenter

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