i18n-string-add

To add bilingual UI strings to Next.js i18n JSON files, insert the new translation key into both ko.json and en.json while maintaining alphabetical order. This ensures Korean and English locale files stay synchronized without manual file edits.

The best way to update multiple locale files for a new Next.js feature is to use dual locale insertion that adds the same key to both ko.json and en.json simultaneously. This approach prevents misaligned translations by validating line counts match across files.

Yes, you can detect the correct i18n namespace from a TSX component automatically. Namespace detection analyzes the consuming React component to determine which JSON locale file section the new translation key belongs to.

Yes, adding new translation keys requires rebuilding the frontend to validate changes. Running the build confirms that both ko.json and en.json updates are syntactically correct and that line counts match across locale files.

Korean and English locale JSON files have mismatched keys after manual edits because updating multiple locale files by hand is error-prone. Automated dual locale insertion enforces alphabetical ordering and matching line counts to prevent sync issues.

A limitation of adding bilingual strings to Next.js i18n JSON files is that the process specifically targets Korean and English locales, requiring both ko.json and en.json to exist. It also mandates a frontend rebuild after every translation key insertion.