Remove extraneous i18n dependency from i18n setup
#11789
Merged
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
Tobbe
added
release:chore
Philzen
added a commit
to Philzen/redwood
that referenced
this pull request
Dec 29, 2024
Philzen
added a commit
to Philzen/redwood
that referenced
this pull request
Dec 30, 2024
Tobbe
added a commit
that referenced
this pull request
Jan 16, 2025
Co-authored-by: Tobbe Lundberg <[email protected]>
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.
I upgraded the i18n-next stack in our Redwood application today and dug a little through the transitive dependencies.
It appears that
i18nis not a very actively maintained package that is still in pre-v1.Neither
i18next, norreact-i18nextori18next-browser-languagedetectordepend on it.Hence it can be safely removed tidying up your dependency tree a bit.