Do not send i18n config to next config when app dir #76
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Well, it seems that the is not building, I tried to downgrade to 13.4.7 as you have in the example, but it works locally, not on Vercel, probably will have to use i18next |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[x ] Bug fix
[ ] New feature
[ ] Other, please explain:
What changes did you make? (Give an overview)
lastest next does not work with i18n confing in next config when using app directory - routing will not work
try https://github.com/aralroca/next-translate/tree/master/examples/with-app-directory with latest next and you will see
Which issue (if any) does this pull request address?
#75
Is there anything you'd like reviewers to focus on?