Localized pathnames on large websites #1209
Unanswered
jjjuulliiaann
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Good question! The If you'd like to reduce the footprint of this config, I think there are currently 3 options:
Hope this provides some help! |
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!
in the docs the recommended approach for localized pathnames is the pathnames object, that needs to exist on build time and is used by the middleware.
This is really useful, as the next-intl link component can resolve all provided pathnames, but I was wondering if this approach is also recommended when you have a lot of locales (~40) and hundreds of urls with localized pathnames (with urls that can also be created independently from new builds).
Would you still try to collect all localized pathnames during build and can this have any performance impact? Or would you rather use some dynamic pathnames with the disadvantage that next-intl doesn't know about the localization of all pathnames?
Some feedback on this would be really helpful. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions