Releases: i18nexus/next-i18n-router
Releases · i18nexus/next-i18n-router
v5.1.0
v5.0.2
v.5.0.1
v5.0.0
To encourage best practices, we have removed the 'rewrite'
routing strategy and require use of a dynamic segment.
Breaking Changes
If you are currently using routingStrategy: 'dynamicSegment'
, no changes are required aside from removing the routingStrategy
option from your config.
routingStrategy
config option removed as now there is only one option ('dynamicSegment'
)- Dynamic segment for the path locale now required
- Removed
currentLocale
helper function. This function used a header set in the middleware to get the current locale, but this was undependable due to middleware response caching. Reading headers in server components also disables use of SSG. To get the current locale in server components, you can now just use the page params.
v4.1.2
- Fix bug in
localeDetector
when no accept-language header present on request (https://stackoverflow.com/questions/76447732/nextjs-13-i18n-incorrect-locale-information-provided)
v4.1.1
v4.1.0
v4.0.0
Breaking Changes
i18nRewriter
has been removed as it is no longer needed. 🎉i18nRouter
no longer accepts an existing response as a third argument.
New Features
- Adds new option named
routingStrategy
that can be set to"rewrite"
(default) or"dynamicSegment"
. The"rewrite"
strategy is the same functionality as v3. The"dynamicSegment"
strategy allows for using the current locale as a dynamic segment, enabling usage ofgenerateStaticParams
for static generation of all languages at build time. Read more here.