fix: localization for "go back home" button on error page

[Adebesin-Cell]

Changes

• Added cursor-pointer to the "Go back home" button in app/error.vue.
• Replaced hardcoded text with $t('common.go_back_home') (if available).
• Added cursor-pointer to NuxtLink in Base.vue to ensure consistent button-like link behavior.

Verification

Before (current behavior – not working as expected):

• Navigate to npmx.dev/non-existent-page
• Hover over the "Go back home" button
• Cursor does not change to pointer

After (with this fix):

• Navigate to npmx.dev/non-existent-page
• Hover over the "Go back home" button
• Cursor changes to pointer and navigation works correctly

[vercel]

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

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

2 Skipped Deployments

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the error view component to use dynamic translation lookup for a button label. The button previously displayed static text "go home" and now references a translation key {{ $t('common.go_back_home') }}. The underlying click handler and control flow remain unchanged, with the button still invoking the handleError method. This is a minimal change affecting a single line of code with no modifications to exported or public entity declarations.

Suggested reviewers

• 43081j
• whitep4nth3r

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main
Description check	✅ Passed	The pull request description clearly describes changes related to the changeset, including localization updates and cursor styling for the error page button.

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

✨ Finishing touches

🧪 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.}

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

[ghostdevv]

I removed the cursor changes since in #1074 I believe we've decided to only use cursor-pointer on links which is the browser default behavior 🙏 If there is a link that is missing cursor-pointer you could make a PR to fix the underlying cause?

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

app/error.vue (1)

54-60: ⚠️ Potential issue | 🟡 Minor

Missing cursor-pointer class mentioned in PR objectives.

The PR description states that cursor-pointer was added to the "Go back home" button, but this class is not present on line 56. Without it, the cursor may not change to a pointer on hover, which was the original issue this PR aimed to fix.

,

🔧 Proposed fix to add cursor-pointer

       <button
         type="button"
-        class="font-mono text-sm px-6 py-3 bg-fg text-bg rounded-lg transition-all duration-200 hover:bg-fg/90 active:scale-95"
+        class="cursor-pointer font-mono text-sm px-6 py-3 bg-fg text-bg rounded-lg transition-all duration-200 hover:bg-fg/90 active:scale-95"
         `@click`="handleError"
       >

[Adebesin-Cell]

I removed the cursor changes since in #1074 I believe we've decided to only use cursor-pointer on links which is the browser default behavior 🙏 If there is a link that is missing cursor-pointer you could make a PR to fix the underlying cause?

Do you mean to add cursor-pointer to links that might have been missed?

[ghostdevv]

I removed the cursor changes since in #1074 I believe we've decided to only use cursor-pointer on links which is the browser default behavior 🙏 If there is a link that is missing cursor-pointer you could make a PR to fix the underlying cause?

Do you mean to add cursor-pointer to links that might have been missed?

Ah, I mean like we can add it if we find it's missing I think? I would've merged it tbf if I was more sure, but I think that the i18n was important to get in soon. Maybe you can make another PR to add the cursor-pointer to linkbase if we want to be sure? I'll then get a review from Alex maybe