feat(i18n): add Korean translations

[yeonjulee1005]

🔗 Linked issue

🧭 Context

Adds Korean (ko-KR) translations and registers the locale.

📚 Description

Added a new ko-KR.json locale and updated config/i18n.ts accordingly.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Jun 19, 2026 9:53pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Jun 19, 2026 9:53pm
npmx-lunaria	Ignored		Jun 19, 2026 9:53pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ea798f98-4407-46d2-921e-ecee5797b4c5

📥 Commits

Reviewing files that changed from the base of the PR and between 8c569ad and b6f888d.

📒 Files selected for processing (2)

• config/i18n.ts
• i18n/locales/ko-KR.json

---

📝 Walkthrough

Summary by CodeRabbit

• New Features
  • Added complete Korean language support across the application interface, including navigation, search, documentation, and all user-facing text and messages.

Walkthrough

The ko-KR locale entry is re-enabled in config/i18n.ts, and the complete i18n/locales/ko-KR.json file (1,788 lines) is added, providing Korean translations for all application UI surfaces including navigation, package pages, comparison, code viewer, account management, and static/legal pages.

Changes

Korean (ko-KR) locale activation

Layer / File(s)	Summary
Locale registration in config config/i18n.ts	The ko-KR object is uncommented in the locales array, making it active for currentLocales, datetimeFormats, numberFormats, and pluralRules derivation.
Core UI and navigation strings i18n/locales/ko-KR.json	Adds the top-level JSON structure, SEO strings, footer links, global shortcuts, command palette, search UI, main navigation, blog section, settings page, noodles feature, and shared error/common labels (lines 1–386).
Package, profile, and org/team strings i18n/locales/ko-KR.json	Adds Korean strings for package detail pages, profile pages, leaderboard, connector/operations UI, and organisation/team/member management screens (lines 387–1017).
Code viewer, comparison, claim, and account strings i18n/locales/ko-KR.json	Adds Korean strings for the package name claim modal, code viewer, badges, filters, package comparison feature, and account/header dropdown (lines 1018–1524).
Static, legal, and brand page strings i18n/locales/ko-KR.json	Adds Korean strings for the about page, privacy policy, accessibility page, translation status page, vacations announcement, action bar shortcuts, brand page, and changelog (lines 1525–1788).

Possibly related PRs

• npmx-dev/npmx.dev#2639: Also modifies config/i18n.ts to add a new locale (pt-PT) to the locales array using the same registration mechanism.
• npmx-dev/npmx.dev#2809: Also touches config/i18n.ts locale registration and adds a locale JSON file through the same i18n wiring code path.

Suggested reviewers

• graphieros

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat(i18n): add Korean translations' accurately summarises the main change, which is adding Korean language support through locale configuration and translation files.
Description check	✅ Passed	The description is directly related to the changeset, clearly explaining that Korean translations are being added and the locale is being registered in the configuration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Hello! Thank you for opening your first PR to npmx, @yeonjulee1005! 🚀

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any issues you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Vercel

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[graphieros]

Thank you! 🌿

I do not speak Korean, and could only check with translation tools, and LGTM.

[yeonjulee1005]

@graphieros Thank you for your review! 😉
I've translated it into the language frequently used by Korean developers~!
I'll continue to contribute whenever needed!
how can I become a maintainer?

[kimkanu]

Hi! Sorry to bother, but I also have created a pull request #2862 2 weeks ago with the same feature. Could you check that out as well?

[yeonjulee1005]

@kimkanu
Oh, I see there was a previous PR submitted. My apologies for missing that.

However, after reviewing the PR you mentioned, it seems to include a koreanModifiers converter for handling Korean particles (e.g., 은/는, 이/가).
I believe this may introduce additional complexity and increase the number of maintenance points in the codebase.

In our case, I think it would be better for native Korean developers to participate directly in the translation process instead.

@graphieros , I would also appreciate your input on this matter.

[graphieros]

@graphieros , I would also appreciate your input on this matter.

@yeonjulee1005, as a non Korean speaker, I can only trust you find an agreement on an approach that is most maintainable and accurate.

[kimkanu]

@yeonjulee1005 , thank you for your considerate comment.

Personally, as another native speaker of Korean language, I think choosing the correct josa is one of the most important feature of Korean translation. I find it very distracting if there's something wrong with josa, or the page is using something like "은(는)" to include both cases. Not only that they seem imperfect and not caring Korean readers, but also it could be distracting for screen reader users because the pronunciations are quite different -- though I'm not a screen reader user, so I'm not 100% sure on this point.

I agree on the point that using bunch of custom modifiers makes the code complicated, especially compared to other languages. And my code has a lot of heuristics which are incorrect under a handful of circumstances.

I'm really open to find a good sweet spot between complexity and correctness. :)

[yeonjulee1005]

@kimkanu

I totally agree with your point on josa it's genuinely one of the trickiest parts of Korean, and getting it wrong breaks the reading flow immediately for native speakers.

That said, I think the most pragmatic sweet spot here might be simpler than any heuristic: leave Korean-specific grammar decisions to native Korean-speaking contributors.
Josa correctness is hard to automate well, and the edge cases are numerous enough that even clever heuristics will occasionally produce something that sounds off.

So rather than trying to solve it in code, it might be worth setting a contribution guideline that Korean translations should be reviewed or contributed by native speakers, similar to how some projects handle RTL languages or complex scripts.

Happy to help improve the Korean translations directly if that's useful! 😊