In order to trigger regeneration, I have added const revalidatedAt = new Date().toISOString() so that the props will be updated every time I visit the page.
I have noticed that during the build on vercel (or in general), the first item that getStaticProps receives is empty (but locale is set) and the paths from getStaticPaths are valid.
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
I'm trying to find out why static revalidation seems to be disabled while using i18n routing.
Here is a quick demo: https://nextjs-i18n-static-error.wiesson.vercel.app, here is the repo: https://github.com/wiesson/nextjs-i18n-static-error/blob/fix/pre-generation/pages/posts/%5Bslug%5D.js
https://nextjs-i18n-static-error.wiesson.vercel.app/posts/123_a or https://nextjs-i18n-static-error.wiesson.vercel.app/en/posts/123_a does not regenerate with the code below.
In order to trigger regeneration, I have added
const revalidatedAt = new Date().toISOString()
so that the props will be updated every time I visit the page.I have noticed that during the build on vercel (or in general), the first item that
getStaticProps
receives is empty (but locale is set) and the paths fromgetStaticPaths
are valid.Originally posted by @wiesson in https://github.com/vercel/next.js/discussions/18443