Not able to view the browser preview, while using next-intl package

I own a online tools website. All Built using v0, but recently I decided to go multi-lingual by supporting multiple languages(locales) and to achieve this in nextjs the current best option is next-intl library. I researched a lot, created the necessary translations, the foundational set up and everything, spending 15$-20$ in credits.

But when I actually installed the next-intl library the v0’s browser view is not working at all. It says that next-intl library is not supported for previewing. I then had to restore back the older version. Which wasted around 20$ and lot of time.

So tell me is this any temporary issue or this is going to stay for ever? because I tried implementing the i18n infrastructure setup in custom way but it is giving a lot of errors and it is not scalable. There are other libraries present but they are not as reliable as next-intl.

So what to do now? We really want to go Multi-Lingual, and for that we have to use next-intl package, if we use next-intl package the v0 browser preview is not working at all. So this is the main issue I am facing right now.

Please Look into this matter asap and confirm me once whether this is going to get fixed sooner or no? Because a lot of our Next steps is dependent on this feature(multi-language support).

I want to know when will this be fixed? Because this is a very important feature or step for our startup. I cannot afford to not leave this feature for long time.

I have attached the image files, so please check it to see the actual issue.

Also I want to know is there any way that I can get the credits back? because I was unaware of the v0’s limitations with respect to this internationalization.

Hey, Amit! :waving_hand:

The v0 in-editor/onsite preview does not currently support next-intl. As you’ve tried, there is an error. You can still use next-intl in your project, the only limitation only affects the v0 preview environment, not your actual app.

Most people validate their internationalization setup by deploying to a Vercel preview deployment instead.

There no confirmed ETA for native preview support yet, but we’ll pass it onto the team.

1 Like

Hi @pawlean , thanks for the clarification,

I have switched to using Vercel preview deployments for now and they work fine, but the in-editor browser preview tab is so much convenient and saves a lot of time. We Have to wait a few minutes for every minor or major change to deploy and then test, this slows down the workflow quite a bit.

I hope that v0 team brings an update where the next-intl is supported in the v0.app browser preview tab itself. This would be so much of convenience for many of us.

But other than this its v0 has been excellent.

1 Like