Bug report

The current version of the react-intl example was simplified by @longlho in #16215 but it keeps the usage of a custom server

Describe the bug

The custom server prevents usage of the serverless build target, which also prevents it from using it with Vercel.

I'm currently running a version of the previous example without the custom server by moving all the detection logic client-side.
This works but sacrifices UX by reloading languages and rerendering when loading a page.

I would prefer to find a solution using react-intl as I find it's API to be better than what next/react-i18next offer.

To Reproduce

not applicable

Expected behavior

Ideally we reach a similar solution to next-i18next which makes this possible across all targets supported by Next.js

Screenshots

not applicable

System information

• Version of Next.js: 9.5.2
• Version of Node.js: 14 (development), 12 (Netlify functions)

Additional context

I'm currently researching solutions to this problem for a project that might move to blitz-js, and found this to be an open issue there, blitz-js/blitz#279