Live data from Hacker News

Multiple domains and languages on the same Next.js site

11–12 of 12 posts

Re: Multiple domains and languages on the same Next.js site

#11

Post by darkteflon » Sun, Apr 11, 2021, 12:00 AM UTC

gigel82 wrote: post #8

The biggest thing missing for i18n is `next export` support; that's the only way to get true SSR (static exports) for something like GitHub pages. It's a shame they haven't addressed that in months despite lots of folks asking for it.

I ran into this (surprising) problem. Ended up having to shift my deployment from Netlify to Vercel itself to get around it.

Re: Multiple domains and languages on the same Next.js site

#12

Post by agustif » Mon, Apr 12, 2021, 11:44 AM UTC

avipars wrote: post #5

languages refer to i18n and not programming languges

Funny because I thought it was programming langugages, as I have done that in the past.

You can mix any supported /api serverless functions runtime in your backend code.

I've done so with python and node for example.

Gotta love next

Post reply on HN