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
This ticket needs done in coordination with the larger effort to migrate to the Next.js App Router: #66
This is based on a comment from the maintainer of next-i18next:
next-i18next
It just means next-i18next is not necessary anymore: https://locize.com/blog/next-13-app-dir-i18n/ https://github.com/i18next/next-13-app-dir-i18next-example
My read of this is that next-i18next will only remain relevant for sites using the "pages" router.
The text was updated successfully, but these errors were encountered:
This will happen as part of the migration to the App Router, which includes a move to using next-intl instead of i18next
next-intl
i18next
Sorry, something went wrong.
No branches or pull requests
Blockers
This ticket needs done in coordination with the larger effort to migrate to the Next.js App Router: #66
Details
This is based on a comment from the maintainer of
next-i18next
:My read of this is that
next-i18next
will only remain relevant for sites using the "pages" router.The text was updated successfully, but these errors were encountered: