6 ms·
It would be great if you guys can take another look at https://github.com/vercel/next.js/issues/18318 https://github.com/vercel/next.js/issues/18318 , lots of f
by gigel82 6y ago
It would be great if you guys can take another look at https://github.com/vercel/next.js/issues/18318 https://github.com/vercel/next.js/issues/18318 , lots of folks seem affected by it.
Basically, there is no way to produce a truly static / SSR ( `next export`) build with i18n; this means one cannot host a multi-language site on a free hosting solution like GitHub pages.
- leerob 6y agoThanks for the feedback! Next.js' i18n support adds a routing and language detection layer, which can't be easily replicated with `next export`. We're open to contributions for this, but it is a difficult problem to solve. Feel free to leave implementation suggestions on that issue.