Jan Amann

So it turns out just a few hours after my comment Next.js 14.1 was released—which seems to fix the issue :). https://github.com/amannn/next-intl/pull/790 furthermore includes a relevant fix for you. Updating...

@bim-oulabi Can you open a new issue with a reproduction?

> Newest Next.js version 14.2.3 breaks it down again, downgraded to Next.js 14.1.4 (with next-inl 3.13.0) and it works Seems like, there was a new report about this in https://github.com/amannn/next-intl/issues/1066....

Having the same issue, there's a workaround that can be applied in `theme.config.tsx` though: ```tsx import {Navbar} from 'nextra-theme-docs'; // ... navbar: { component: function CustomNavbar({ items, ...rest }: ComponentProps)...

A reproduction would be important to look into this, but based on the stack trace, it could be that your error is caused by this misconfiguration: [Unable to find locale](https://next-intl-docs.vercel.app/docs/routing/middleware#unable-to-find-locale)....

Interesting. If you could provide some more information or ideally a reproduction, that would be helpful. There was another report about 13.14, we were able to resolve that: https://github.com/amannn/next-intl/issues/1072

I don't see an issue with that code. Can you try to isolate the issue to a particular line that causes the issue? Can you also post your `i18n.ts`?

@ilikali Were you able to figure out a solution eventually? "default" is in any case not a valid locale. The locale is not only used for reading messages, but also...

Uh, that really asks for trouble. As mentioned above, "default" is not a valid locale and you should really use `az` or `ru` to initialize APIs from `next-intl`. I'd in...

That sounds reasonable, thanks for the proposal! Just some minor remarks: 1. We had a similar PR for `Link`: https://github.com/amannn/next-intl/pull/257. Can we make sure that we share the detection wether...