Open redirect vulnerability ### Impact Applications using the `next-intl` middleware with `localePrefix: 'as-needed'` could construct URLs where path handling and the WHATWG URL parser resolved a relative redirect target t...

📣 PSA: If you're using `localePrefix: as-needed` in your next-intl routing configuration, please be sure to update to next-intl@4.9.1

github.com/amannn/next-...

It should work for this use case too, can you share a reproduction based on github.com/amannn/nextj...?

Maybe I missed something …

There's also github.com/amannn/next-... btw. for sharing such feedback.

My demo is also using AsyncLocalStorage from Node.js, it's pretty handy!

Not sure if you can really call it a solution since it only works for self-hosted setups :). But yes, global state per request is what this does.

GitHub - amannn/nextjs-request-store Contribute to amannn/nextjs-request-store development by creating an account on GitHub.

github.com/amannn/nextj...

Black-magic Next.js hack of the week 🧙‍♂️

→ When self-hosting, you can pass request headers from a custom server to the rendering process without opting into dynamic rendering.

next-intl@4.8.1 is out with a minor fix for Windows, please keep the feedback coming!

next-intl.dev/blog/precomp...

🌐 next-intl 4.8 is out with ahead-of-time compilation!

Flip the 𝚙𝚛𝚎𝚌𝚘𝚖𝚙𝚒𝚕𝚎 flag and drop ~9KB of compressed JS from your bundles.

With ahead-of-time compilation of messages, while using an ultra-slim AST! It not only decreases your bundle size, but also improves runtime performance. It’s been on my roadmap for a long time, I‘ll share more in a blog post!

The slimmest next-intl ever is coming to a 𝚗𝚘𝚍𝚎_𝚖𝚘𝚍𝚞𝚕𝚎𝚜 folder near you this week.

You‘re gonna love the upcoming next-intl release … This was feature was on the roadmap for 3 years!

Build international Next.js apps with confidence Learn how to build delightful, multilingual experiences with the official next-intl course.

This is the first batch.

Definitely keep an eye out, as I'll be adding more over time and existing members automatically get access at no extra cost.

Got a tricky setup that isn’t covered yet? Just let me know!

learn.next-intl.dev

4 templates: - app-router-auth - app-router-saas - app-router-tenants - app-router-monorepo

Starter templates are here on 🌐 learn.next-intl.dev!

code.visualstudio.com/docs/getstar...

If you're not using 𝚠𝚘𝚛𝚔𝚋𝚎𝚗𝚌𝚑.𝚎𝚍𝚒𝚝𝚘𝚛.𝚌𝚞𝚜𝚝𝚘𝚖𝙻𝚊𝚋𝚎𝚕𝚜.𝚙𝚊𝚝𝚝𝚎𝚛𝚗𝚜 in your IDE yet, you should turn it on today.

Really cool! 🙌

About to create the repo on GitHub …

I'm thinking about adding a set of premium templates for members of 🌐 learn.next-intl.dev

E.g.:
- Auth integrations
- E-commerce integrations
- CMS integrations
- Advanced cases like multi tenancy

Anything you found challenging that you think would be useful to include?

All good, I surely had to laugh at the hair salon reference 😄

This library is PAINFULLY slow on Nextjs, specially when integrating route based locales. DO NOT USE THIS LIBRARY IF YOU'RE NEW TO INTERNATIONALIZATION... · amannn next-intl · Discussion #2190 I'm sorry but i have to be this guy, if you're new to translations, internationalization, this library is not for you, even if it seems easy to set up, bugs, cache issues, rtl issues, and other stu...

If you're looking for an i18n library that causes a "compile time that takes longer that a hair salon appointment", then I've got your back 🤝

github.com/amannn/next-...

… and then, you can of course pass the errors to the client side.

Code snippet that demonstrates how to use an error map in Zod 4 for computing errors.

Contextual, localized error handling in Server Actions with Zod 4 — the easy way.

Many thanks to everyone who is actively helping with feedback to get this to stability as quick as we can. I'm adding a test for every edge case that we discover to make sure this remains fixed once the root cause has been addressed.

Another week, and another release of next-intl is out with fixes for useExtracted.

In case you're already using this feature, it's recommended to upgrade!

github.com/amannn/next-...

Release v4.6.0 · amannn/next-intl 4.6.0 (2025-12-12) Features Custom formats for useExtracted, consistency fixes for file references, pruning of messages and sorting of keys (#2155) (c02818e) – by @amannn

Release notes →

github.com/amannn/next-...

useExtracted (experimental) – Internationalization (i18n) for Next.js Internationalization (i18n) for Next.js

Docs on custom formats →

next-intl.dev/docs/usage/e...

🌐 next-intl@4.6 is out!

You can now define custom codecs for useExtracted if you have more specific needs than what ships out of the box.

This release also includes further fixes for message extraction, so definitely upgrade if you're already adopting this!

Awesome, thanks!

Fwiw my current todo list is more on the docs side, I’m not aware of currently open bugs: github.com/amannn/next-...

If you have specific questions, don’t hesitate to reach out! (Ideally in the linked discussion, so others can chime in as well)

Cool! I know that some startups have already migrated to useExtracted and it works pretty well for them. I’m dedicated to fix all bugs that appear as quickly as I can. It’s still declared as experimental, but if you’d like to help stabilizing I’d certainly appreciate it.