fix(docs-site): upgrade Docusaurus 3.10.0 → 3.10.1 to restore KO i18n - #115
Conversation
Closes #114. Docusaurus 3.10.0 had a regression (facebook/docusaurus#11952) where i18n locale path resolution used `htmlLang` instead of the locale key. Our `localeConfigs.ko.htmlLang = 'ko-KR'` caused Docusaurus to look for files at `i18n/ko-KR/` instead of `i18n/ko/`, silently falling back to EN source for every KO doc page. Effect on production /ko/docs/*: only theme chrome (skip-to-content, sidebar labels) was translated; markdown body content rendered EN regardless of locale. Verification (build/ko/docs/intro/index.html): before: 0 hangul matches for "Kalyx 가 존재", "완성된 상태로" after: multiple matches for both phrases The fix landed upstream as PR facebook/docusaurus#11979 and was backported to 3.10.1. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 38 minutes and 45 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
번들 크기가 목표 이내입니다. |
1 participant
Closes #114.
Root cause
Docusaurus 3.10.0 had a regression (facebook/docusaurus#11952) where the i18n locale path resolution used
htmlLanginstead of the locale key. Our config has:```ts
localeConfigs: {
ko: { label: '한국어', htmlLang: 'ko-KR' },
},
```
So Docusaurus 3.10.0 looked for translated files at `i18n/ko-KR/...` (using `htmlLang`) instead of `i18n/ko/...` (using the locale key). When it didn't find them, it silently fell back to the EN source.
Effect on production
Every `/ko/docs/` page rendered the EN markdown content, even though the KO source files (`i18n/ko/docusaurus-plugin-content-docs/current/.md`) exist and contain full translations. Only Docusaurus's own theme chrome (skip-to-content, sidebar collapse buttons, breadcrumbs) was localized via `code.json`.
Fix
The upstream fix is facebook/docusaurus#11979, backported to 3.10.1. This PR bumps all seven `@docusaurus/*` packages from 3.10.0 → 3.10.1.
No config changes needed — `localeConfigs.ko.htmlLang: 'ko-KR'` is correct and recommended for SEO (`` attribute).
Verification
Local build `pnpm exec docusaurus build` followed by:
```bash
grep -c "Kalyx 가 존재\|완성된 상태로" build/ko/docs/intro/index.html
3.10.0 → 0
3.10.1 → 6 (after upgrade)
```
The KO intro page, comparison page, every component doc, recipe, and concepts page now renders the Korean markdown body content, not the EN fallback.
Test plan
🤖 Generated with Claude Code