feat: use navigation builder for desktop and mobile links

[bdbch]

This PR moves the navigation into it's own configuration object to make the configuration for both - desktop & mobile easier & less prone for errors.

[vercel]

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

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

2 Skipped Deployments

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

[bdbch]

Looking into the Type errors right now.

[codecov]

Codecov Report

❌ Patch coverage is 19.04762% with 17 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
app/components/Header/MobileMenu.client.vue	0.00%	10 Missing ⚠️
app/components/AppHeader.vue	36.36%	5 Missing and 2 partials ⚠️

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR introduces typed navigation types in app/types/navigation.ts and re-exports them via app/types/index.ts. AppHeader.vue gains computed desktopLinks (NavigationConfig) and mobileLinks (NavigationConfigWithGroups), replaces hard-coded desktop navigation and per-link keyboard handlers with data-driven logic, and passes mobileLinks into the mobile menu. Header/MobileMenu.client.vue now accepts a links prop of type NavigationConfigWithGroups and renders grouped navigation (including separators and optional group labels) dynamically instead of static link blocks.

Possibly related PRs

• fix: reorder Mobile Menu #1185: Modifies app/components/Header/MobileMenu.client.vue — overlaps with this PR’s changes to make the mobile menu data-driven and reorder its structure.

Suggested labels

front

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, explaining that navigation configuration has been refactored into a dedicated object structure for both desktop and mobile.

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

---

No actionable comments were generated in the recent review. 🎉

---

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

[coderabbitai]

Actionable comments posted: 5

🧹 Nitpick comments (1)

app/types/navigation.ts (1)

15-17: Consider adding an optional identifier to NavigationSeparator.

Adding a name property to NavigationSeparator would enable consistent keying in Vue templates (as seen with NavigationGroup.name) and avoid relying on array indices.

♻️ Suggested enhancement

 export type NavigationSeparator = {
+  name?: string
   type: 'separator'
 }

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

Actionable comments posted: 1

[github-actions]

Thanks for your first contribution, @bdbch! 💫

We'd love to welcome you to the npmx community. Come and say hi on Discord! And once you've joined, visit npmx.wamellow.com to claim the contributor role.