fix(i18n): update norwegian translation

[bonsak]

This commit adds missing keys and values to the Norwegian translation
It also renames previous locale (no-NO) to nb-NO (Bokmål) to open for nn-NO (Nynorsk) translation in the feature.

[vercel]

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

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

2 Skipped Deployments

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

[coderabbitai]

📝 Walkthrough

Walkthrough

This change renames the Norwegian locale entry in config/i18n.ts from code no-NO/file no-NO.json/name Norsk to nb-NO/nb-NO.json/Norsk (Bokmål) and adds a new, expanded nb-NO.json. The new locale file introduces many translation keys and objects (shortcuts, search enhancements, data_source, provenance_section, likes, size, no_dependency, privacy_policy, default_input_error, and other UI strings), plus a top-level $schema entry.

Possibly related PRs

• feat(i18n): add support for norwegian language #1104: Previously added a Norwegian locale entry (no-NO) that this PR renames/replaces with nb-NO.
• feat(i18n): add missing zh-CN translations for shortcuts, data source… #1250: Adds the same i18n keys (shortcuts, data_source, search.* and atmosphere.default_input_error) to other locale files—parallel localization changes.
• chore(i18n): generate JSON Schema for locale files #1249: Introduces or standardises the top-level $schema metadata across locale files, matching the $schema addition in nb-NO.json.

Suggested reviewers

• danielroe
• serhalp

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description accurately describes the changeset: adding missing translation keys to Norwegian and renaming the locale from no-NO to nb-NO (Bokmål).

_{✏️ 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

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

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

Actionable comments posted: 1

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Remove duplicate keys that override translations.

Line 259 and Line 1057 re‑declare provenance_section and privacy_policy. In JSON, the last key wins, so the populated translations are discarded. Please remove the empty duplicates.

🧹 Suggested fix

@@
-    "provenance_section": {},
     "security_downgrade": {},
@@
-  "privacy_policy": {
-    "cookies": {
-      "what_are": {},
-      "types": {},
-      "local_storage": {},
-      "management": {}
-    },
-    "analytics": {},
-    "authenticated": {},
-    "data_retention": {},
-    "your_rights": {},
-    "contact": {},
-    "changes": {}
-  }

Also applies to: 977-1070

🧰 Tools

🪛 Biome (2.3.14)

[error] 250-250: The key provenance_section was already declared.

This is where a duplicated key was declared again.

If a key is defined multiple times, only the last definition takes effect. Previous definitions are ignored.

(lint/suspicious/noDuplicateObjectKeys)