Skip to content
New issue

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

Remove next-i18next as a dependency #164

Closed
sawyerh opened this issue Jun 30, 2023 · 1 comment
Closed

Remove next-i18next as a dependency #164

sawyerh opened this issue Jun 30, 2023 · 1 comment
Labels
i18n Internationalization / Translation

Comments

@sawyerh
Copy link
Contributor

sawyerh commented Jun 30, 2023

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:

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.

@sawyerh sawyerh added the i18n Internationalization / Translation label Jun 30, 2023
@sawyerh sawyerh added this to the Next.js App Router milestone Nov 8, 2023
@sawyerh sawyerh changed the title next-i18next is not necessary for Next.js 13's App directory Remove next-i18next as a dependency Nov 8, 2023
@sawyerh
Copy link
Contributor Author

sawyerh commented Nov 29, 2023

This will happen as part of the migration to the App Router, which includes a move to using next-intl instead of i18next

@sawyerh sawyerh closed this as completed Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n Internationalization / Translation
Projects
None yet
Development

No branches or pull requests

1 participant