Next.js 15 example with Tolgee and next-intl?

[empz]

I need to migrate my Next.js 14 app to v15. I'm currently using Tolgee following the setup shown here: https://github.com/tolgee/next-app-intl-example

After upgrading, I'm getting errors because of the breaking changes Next 15 introduced.

[Error: Route "/[locale]" used `headers().get('X-NEXT-INTL-LOCALE')`. `headers()` should be awaited before using its value. Learn more: https://nextjs.org/docs/messages/sync-dynamic-apis]
Deprecation warning: `useLocale` has returned a default from `useParams().locale` since no `NextIntlClientProvider` ancestor was found for the calling component. This behavior will be removed in the next major version. Please ensure all Client Components that use `next-intl` are wrapped in a `NextIntlClientProvider`.

Are there any docs or repos to aid with this migration?

[empz]

So I actually noticed the sample repo here is on Next 15, even though the README says 14.

I've followed everything that's there to match with my project but I'm getting a Deprecation warning in both the server and browser console:

Deprecation warning: `useLocale` has returned a default from `useParams().locale` since no `NextIntlClientProvider` ancestor was found for the calling component. This behavior will be removed in the next major version. Please ensure all Client Components that use `next-intl` are wrapped in a `NextIntlClientProvider`.

I'm not directly calling any of these hooks (useLocal or useParams) anywhere in my app so it might be some miss configuration or something. Any ideas?

[empz]

Actually, that sample repo has bad types...

[stepan662]

Hey, I don't think this is connected to the upgrade to next 15, these kind of errors are happening when there is some misconfiguration in tsconfig. Are you using standard next.js tsconfig?

[empz]

That's not my repo, that's a screenshot of the sample repo at https://github.com/tolgee/next-app-intl-example. But I've just opened it in a Codespace and those imports exist. It might have been a node_modules issue.

Any ideas on my original issue? After upgrading to Next 15, my translations are not working on a production build.

[stepan662]

The newest version of the package should be compatible with the next.js 15. I think we had these deprecation warnings in older version, but that should be fixed. As you said, we are actually using next.js 15 in the example app.

When I run our example app, I don't have these deprecation warnings, so I would need some way how to replicate your issue.