We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Originally posted by FenderFred June 8, 2023 Hi,
Is it true that the middleware for localization can be running on NextJs SPA (output: export) ? I see this in the documentation of Client side component: https://next-intl-docs.vercel.app/docs/next-13/client-components#middlewarets
When I add the middleware without a locale in the path, the defaultLocale in the middleware do nothing. Is it supposed to work ?
Thanks
The text was updated successfully, but these errors were encountered:
c9c2070
Successfully merging a pull request may close this issue.
Discussed in #323
Originally posted by FenderFred June 8, 2023
Hi,
Is it true that the middleware for localization can be running on NextJs SPA (output: export) ?
I see this in the documentation of Client side component:
https://next-intl-docs.vercel.app/docs/next-13/client-components#middlewarets
When I add the middleware without a locale in the path, the defaultLocale in the middleware do nothing.
Is it supposed to work ?
Thanks
The text was updated successfully, but these errors were encountered: