Replies: 1 comment 1 reply
-
Sure, you can compose the middleware and add additional redirects as necessary on top! In this case, you don't want to specify custom prefixes. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone. I'm new to the
next-intl
space and still exploring this i18n library.I have a use case where I want to be able to support 2-letter code prefix routing alongside other locales. I wonder if it is currently possible in
next-intl
.Use case:
/en
redirects to/en-US
/ja
redirects to/ja-JP
/ko
redirects to/ko-KR
/en-US
,/ja-JP
,/ko-KR
renders the page without redirection.Beta Was this translation helpful? Give feedback.
All reactions