update: move next turbo config from experimental to top level

[sakib412]

Ref: #1838

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-intl-example-app-router	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 10, 2025 9:29am
next-intl-example-app-router-without-i18n-routing	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 10, 2025 9:29am

[vercel]

@sakib412 is attempting to deploy a commit to the next-intl Team on Vercel.

A member of the Team first needs to authorize it.

[amannn]

This would unfortunately be a breaking change for users on Next.js <15.3.

Please see the previous discussion here:

• Turbopack and next-intl/plugin - The config property experimental.turbo is deprecated. #1838
• Deprecation warning for experimental.turbo with Next.js plugins (e.g. @next/mdx) vercel/next.js#78009

[sakib412]

This would unfortunately be a breaking change for users on Next.js <15.3.

Please see the previous discussion here:

• Turbopack and next-intl/plugin - The config property experimental.turbo is deprecated. #1838
• Deprecation warning for experimental.turbo with MDX plugin (also affects other downstream plugins) vercel/next.js#78009

Got you! Either we have to wait for to get the nextjs version in next config or we can pass the nextjs version in

createNextIntlPlugin('path', options = {nextVersion: '15.3.0'})

function arg as options. (we can parse the version from package.json or node_modules)
and also this is just a warning we can ignore for now, anyway nextjs will release major version for breaking change.

[amannn]

we can parse the version from package.json or node_modules

I thought about that too, but I'm afraid there could be edge cases. E.g., can we make an assumption about where a package.json file should be? E.g. Next.js supports the [directory] argument for next dev, therefore process.cwd() could be somewhere else.

The closest I could think of would be to use require.resolve('next') to get a path to the Next.js dependency folder and from there traverse upwards to find the closest package.json and read the version from there.

It sounds a bit hairy though and maybe there are edge cases. So ideally, Next.js would help a bit here, let's see if we can get support from them in vercel/next.js#78009.