Description

With the release of Next.js v15.3.0, we can try next build --turbopack.

By doing so with the following next.config.js:

import createNextIntlPlugin from "next-intl/plugin"

const withNextIntl = createNextIntlPlugin()
export default withNextIntl()

It yields this warning:

⚠ The config property `experimental.turbo` is deprecated. Move this setting to `config.turbopack` as Turbopack is now stable.

This is because of those lines:

Is there a way to detect the Next.js version used, and if above than v15.3, then we don't use experimental.turbo, but directly in the turbo property, otherwise we keep current behavior for older versions to avoid breaking changes?

Or maybe, we can't do it automatically, but at least we could provide a param to withNextIntl, to tell that we should put turbo config under turbo property, and not with experimental.turbo.

Verifications

• I've verified that the problem I'm experiencing isn't covered in the docs.
• I've searched for similar, existing issues on GitHub and Stack Overflow.
• I've compared my app to a working example to look for differences.

Mandatory reproduction URL

https://github.com/amannn/next-intl/tree/main/examples/example-app-router

Reproduction description

Steps to reproduce:

1. Install next-intl to a project with Next.js v15.3.0
2. Run next build --turbopack
3. See the warning

Expected behaviour

No warnings.