You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Next's default Link component does not require client-side JavaScript to work.
When using the next-intl Link, routing works for the default locale but not for the others:
For example, while using localePrefix: "never" along with localized pathnames and after disabling JS on the client, theres an infinite redirection loop.
Describe the solution you'd like
Next-Intl's Link to not cause infinite redirection without Client-Side JS.
Describe alternatives you've considered
Not using localePrefix: "never" is an alternative.
The text was updated successfully, but these errors were encountered:
Are you sure that you're seeing an infinite redirection loop? The link should include the locale prefix, but if you click it, it should redirect from the middleware to the non-prefixed version (and stay there).
If you see an infinite redirect, can you provide a reproduction?
Is your feature request related to a problem? Please describe.
Next's default Link component does not require client-side JavaScript to work.

When using the next-intl Link, routing works for the default locale but not for the others:
For example, while using
localePrefix: "never"
along with localized pathnames and after disabling JS on the client, theres an infinite redirection loop.Describe the solution you'd like
Next-Intl's Link to not cause infinite redirection without Client-Side JS.
Describe alternatives you've considered
Not using
localePrefix: "never"
is an alternative.The text was updated successfully, but these errors were encountered: