Description
Is your feature request related to a problem? Please describe.
Since v3 is ESM only and your recommendation is to use v2 is ESM if this is blocking for us, could it be possible to port this improvement to v2?
Indeed, we already had a few instances of a SSR issue in production where the fetched url contained UTF-8 characters and made the fetch fail server-side but not client-side. Those issues are pretty tricky to catch ahead of time if the developer forgets to take UTF-8 into account when building the url.
Describe the solution you'd like
Port the UTF-8 improvement to v2.