This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Add locales to NextURL for access in Middleware
#37253
Comments
ambrauer
added a commit
to Sitecore/jss
that referenced
this issue
May 27, 2022
…3) and use static values for now. next.config.js is not intended to be imported in this way. We should have access to locales directly in middleware in the future: vercel/next.js#37253
3 tasks
illiakovalenko
pushed a commit
to Sitecore/jss
that referenced
this issue
May 30, 2022
…1045) * Remove import of next.config.js in redirects middleware (fixes #535263) and use static values for now. next.config.js is not intended to be imported in this way. We should have access to locales directly in middleware in the future: vercel/next.js#37253 * Add type assist jsdoc for NextConfig
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Describe the feature you'd like to request
The
NextRequestnextUrlprovides other locale info (locale,defaultLocale,domainLocale- which does includelocales), but is notably missinglocales. This is useful information to have particularly in middleware which is handling rewrites and redirects.Describe the solution you'd like
Included the configured i18n locales under a
localesprop onNextURLso that it is accessible onNextRequestin middleware. This would be in line with i18n config accessibility in other areas of the API.Describe alternatives you've considered
Duplicating configured locales in middleware code, or storing locales in common file.
The text was updated successfully, but these errors were encountered: