chore: prevent adding missing entries to wrong locale files

[userquin]

This PR is the continuation of #1063 where we didn't prevent fix wrong locale files (locales):

• country locale files inside country variants cannot be fixed: e.g. running nr i18n:check:fix es-ES is wrong, we should run nr i18n:check:fix es
• target locale inside country variants cannot be fixed: e.g. this is wrong nr i18n:check:fix es-419, since i18n will do the work for us (we should fix only language locale)
• allow run i18n:check:fix: won't save files with mergeLocale: true

This PR also includes a fix when running build:lunaria script, won't add extra \n at the end.

/cc @shuuji3

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 7, 2026 4:07pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 7, 2026 4:07pm
npmx-lunaria	Ignored		Feb 7, 2026 4:07pm

[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!

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request makes two changes to translation tooling: it appends a trailing newline when writing JSON locale files in lunaria/prepare-json-files.ts, and it updates scripts/compare-translations.ts to add a singleLocale parameter and a guard that errors/exits when --fix is used against a merged/variant locale. It also changes when updated JSON is written for localized files to avoid writing for merged locales unless removals or fixes apply to non-merged locales.

Possibly related PRs

• chore: update compare-translations.ts logic #1063: Modifies scripts/compare-translations.ts and lunaria/prepare-json-files.ts with overlapping changes to merged/variant locale guard logic and newline/file-write behaviour.

Suggested reviewers

• danielroe

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description clearly relates to the changeset, describing the prevention of i18n fixes to incorrect locale files and a trailing newline fix in the build script.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 1

[shuuji3]

Thank you. I tested with the same text files in #1063 and existing JSON. And, lunaria doesn't strip the newline at EOF 😀

There's only one remaining issue, when it runs in all locale mode (runAllLocales()) that is without specifying a specific locale in the command, it still try processing ar-EG. We should filter out that such case.

> pnpm run i18n:check:fix

> npmx@0.0.0 i18n:check:fix /home/shuuji3/dev/npmx.dev
> node scripts/compare-translations.ts --fix

Error: Locale "ar-EG" cannot be fixed, fix the ar locale instead!
 ELIFECYCLE  Command failed with exit code 1.

[userquin]

@shuuji3 Changes in this PR will prevent to run nr i18n:check:fix, maybe we can pass a new flag to just ignore the fix when running previous command), the script will fail, the problem is about mix fixing files and collecting info.

[userquin]

There's only one remaining issue, when it runs in all locale mode (runAllLocales()) that is without specifying a specific locale in the command, it still try processing ar-EG. We should filter out that such case.

I'm going to update the logic... syncLocaleData will just ignore the update when mergeLocale is true

[userquin]

@shuuji3 to collect the info, the processLocale won't exit and won't save the files with mergeLocale: true:

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

Actionable comments posted: 1

[shuuji3]

It all seems to be OK now 🙂