Is Nextjs supported ?

[laem]

Obviously Nextjs is mostly react and JSX, so it might.

But I'm surprised to see not mention of Nextjs itself, since it's a framework one of the most well-known one.

I'm planning on i18ning cartes.app, a Web alternative to Google Maps currently French-only, and would love to use an i18n platform that lets us keep clean JSX without everywhere.

I'm particularly worried that the Turbopack version of nextjs, v16, would not work.

Did someone use Wuchale for a Nextjs project successfully ?

[laem]

Also, the examples repo says "Great for client-only React projects".

[K1DV5]

Hi @laem, thank you for reaching out. Nextjs is indeed mostly react and JSX, which are already supported. But the issue is the bundler it uses, as to the best of my knowledge, it doesn't use Vite.

Wuchale currently only supports Vite as a bundler. There is a plan to implement support for Nextjs, which is why @wuchale/vite-plugin is a separate package, to allow it to be used with other bundlers. But currently it's not yet implemented.

[laem]

Thanks ! Next is switching to Turbopack as a default, leaving Webpack.

I don't know enough on this subject to go further. So let's leave this open in case someone stumbles on this. Regards

[K1DV5]

I was thinking about this, and there is one idea I have. For targets that don't use a bundler, it already supports writing the transformed files to disk, another dir, just using the wuchale cli, with a watch mode already available. But I was thinking to make it transform files in-place (to avoid problems with paths changing) with the ability to restore the original files with git. That lets us sidestep the requirement of using a bundler and paves the way to future support for even other languages like Go and Python. Normally you would start wuchale's cli in watch mode, do your thing and it maintains the catalogs in parallel. Then you push your work to CI and the files get transformed in-place in a build step and since the catalogs are maintained in parallel during dev, the output should match. That, paired with the planned --check flag to see if there are any problems beforehand, maybe Next could be supported without a bundler.