fix: consistent error display in development and production

[iiio2]

development and production environment are displaying different error message for non-existent package. I think the local environment is correct here. In production it is likely due to how Nuxt serializes/hydrates errors differently - in production maybe there are ISR/SSR stuffs.

Production:

Development:

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 4, 2026 5:26am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 4, 2026 5:26am
npmx-lunaria	Ignored		Feb 4, 2026 5:26am

[codecov]

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
app/error.vue	0.00%	0 Missing and 2 partials ⚠️

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

The app/error.vue component was updated to align with changes to the NuxtError object structure. The status property now reads from props.error.statusCode instead of props.error.status, maintaining a default value of 500. The statusText property was updated to use props.error.statusMessage instead of props.error.statusText for its initial assignment. These changes reflect updates to how error information is provided by Nuxt, with two lines modified in total. No public entity signatures were altered by these changes.

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description directly addresses the changeset by identifying environment-specific error handling differences and explaining the rationale for updating error property access patterns.

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

Important

Action Needed: IP Allowlist Update

If your organization protects your Git platform with IP whitelisting, please add the new CodeRabbit IP address to your allowlist:

• ✨ 136.113.208.247/32 (new)
• 34.170.211.100/32
• 35.222.179.152/32

Reviews will stop working after February 8, 2026 if the new IP is not added to your allowlist.

---

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

[iiio2]

Thanks @danielroe . 😊