-
Notifications
You must be signed in to change notification settings - Fork 67
i18n fails to build #71
Comments
hey @victorhqc thanks so much for reporting this and for the repro repository π it seems like in next 10, when i18n is included in your next config, the statically generated html now sits in a different folder in the build directory (under each locale), instead of at the path where next-on-netlify is currently looking and erroring aka |
One way to get this working is with Netlify redirects. It's a hacky, not elegant and maintanable at all approach however it gets the job done. |
@georgekpc @victorhqc i'm currently working on this alongside some other work, hoping to have a PR open by end of week |
How? I need this functionality to satisfy a client. π¬ |
Yes! I asked if we could get a prerelease out there. #75 (comment) |
@TejasQ ah so sorry missed it when i saw justin's longer comment π will address that comment! |
same problem here @victorhqc |
merged #75, releasing shortly! |
Hello π
I noticed that I can't build my site when using the new i18n feature. I built dummy repository in which I reproduce the issue.
Te repository that reproduces the issue can be accessed here, just run the following
It is a standard next.js application using:
10.0.0
2.6.0
Something interesting to note is that the site builds correctly when I omit the
getStaticProps
inhello.js
.The text was updated successfully, but these errors were encountered: