It doesnt work with turbopack about next-intl HOT 8 CLOSED

@mifrej There was a recent discussion about this in #898 and it seems like there's movement on the Turbo side in regard to this 🤞

from next-intl.

The App Router example can be started with --turbo. Maybe that helps! It's quite a minimal example at this point but illustrates that next-intl works with Turbo.

I'm personally not using Turbo for commercial projects yet due to other bugs in Turbo I've encountered. I therefore don't recommend using it currently and the support in next-intl is considered experimental. I think for now we might have to wait for the Turbo team to iron out the current issues :).

from next-intl.

Thank you very much @amannn, I'll checkout this App Router example and compare it with my setup.

However like you mentioned, I think I will wait as well before spending more time on this since it is considered experimental with Turbo. Hopefully the latest official releases of NextJS 14 will improve the Turbo experience and setup!

Have a pleasant rest of your day! Again thank you for your contribution! 🙂

from next-intl.

This looks like a duplicate of this: #718 (comment)

Turbopack support is currently experimental. If you want to help here, you can report this bug upstream in the Turbopack repo (in case it hasn't already been reported).

from next-intl.

Hey @amannn I don't know if this can help or give more context but I open this discussion in NextJS Github community:

vercel/next.js#59720

I think the main raison why it's not working with Turbo (at least with my setup) is because when turbo cannot find the middleware.ts which contains the configuration for localization.

What are your thoughts?

(Happy holidays as well!)

from next-intl.

From my experience, the middleware compiles just fine. You're right that the log output doesn't mention the middleware though (not sure if intended).

Happy holidays!

from next-intl.

@amannn thank you for your quick response!

That’s good to know, but could you, when the time permits, share your setup please (similarly like how I shared mine in the nextjs discussion)?

I might be missing something…? I really tried everything by now and I’m kinda starting to feel hopeless 😞. In my case, it gets stuck and no pages are being loaded successfully when using turbo…

I am now on the latest version of nextjs canary + next-intl (3.4.0) + Typescript v5 and still no luck… 🍀

Addionaly, it would be very appreciated if a boilerplate/example with turbo support could be added to the github’s examples or documentation. I’m positive it will help many!

Thank you very much! Sending you positive vibes and looking forward to your reply ~ 🙂

from next-intl.

The example you point to @amannn when using with --turbo flag is not working.
The page remains fixed on one translation only, when with --turbo, whatever route language segment you use.

So bottom line is next-intl does not work with Turbo, but I get the point of --turbo being experimental, just wanted to clarify this here

from next-intl.