We support Dynamic Routes and getStaticProps Pages from next.js? about next-translate-routes HOT 9 CLOSED

It seems like getStaticPaths does not get the translated routes from the _routes.json file.
It looks like it's impossible to combine this library with SSG sadly. I hope this feature will be added soon.

Edit:
I made it work, going to post the solution later.

from next-translate-routes.

Really need this feature too

from next-translate-routes.

Hi, @draxx318 is there any improvements on solution?

from next-translate-routes.

Sorry, I don't get it, could you explain your issue?
I also have some getStaticPaths and it works well...
You should not have anything to do here: getStaticPaths creates the dynamic file paths, which is then redirected and rewritten using next-translate-routes.

from next-translate-routes.

Sorry, I don't get it, could you explain your issue? I also have some getStaticPaths and it works well... You should not have anything to do here: getStaticPaths creates the dynamic file paths, which is then redirected and rewritten using next-translate-routes.

I am facing the same problem : getStaticProps does not work with translated routes
if you refresh the page, props will pass from getStaticProps to the page.
but if you click the Link from translateRoute, the page wont grab props from getStaticProps

from next-translate-routes.

It seems like getStaticPaths does not get the translated routes from the _routes.json file. It looks like it's impossible to combine this library with SSG sadly. I hope this feature will be added soon.

Edit: I made it work, going to post the solution later.

Can't wait to see your solution!

from next-translate-routes.

🤔 Strange... I don't have this issue anywhere. Could you provide a minimal reproduction?

from next-translate-routes.

I just found out that if your file contains middleware.ts, getStaticProps will immediately fail.

from next-translate-routes.

I just found out that if your file contains middleware.ts, getStaticProps will immediately fail.

Yes. See here

So this issue is a duplicate of this one, let's close it.

from next-translate-routes.