-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2: Better UTF-8 URL handling #1290
Comments
|
|
1 task
I've submitted a PR for this here: #1291 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: