Fix incorrect Internationalization import usage in README#15
Merged
Peter080202 merged 1 commit intomainfrom Apr 28, 2026
Merged
Fix incorrect Internationalization import usage in README#15Peter080202 merged 1 commit intomainfrom
Peter080202 merged 1 commit intomainfrom
Conversation
Peter080202
added
documentation
lukasvice
approved these changes
Apr 22, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR fixes incorrect documentation regarding the import of
Internationalizationfrom@aboutbits/internationalization.The docs previously suggested a named import:
However, the package actually exposes
Internationalizationas a default export, so the correct usage is:Why is this change needed?
The previous documentation is misleading and results in a TypeScript error (
TS2614).Tests
N/A (only README file update 🙂)