fix: avoid showing "No README is available" during README load

[akadotsh]

🔗 Linked issue

Closes #2467

🧭 Context

📚 Description

Updated README rendering logic to use fetch status and only show the no-README message after a successful fetch with empty content.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Apr 11, 2026 9:12am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Apr 11, 2026 9:12am
npmx-lunaria	Ignored		Apr 11, 2026 9:12am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cb566424-5407-4054-917f-7d81b118dab9

📥 Commits

Reviewing files that changed from the base of the PR and between 0164064 and 752f8f7.

📒 Files selected for processing (1)

• app/pages/package/[[org]]/[name].vue

---

📝 Walkthrough

Walkthrough

This pull request modifies the package details page to fix a timing issue with README display. The change updates the lazy fetch for README content to expose both the response data and fetch status. The template logic is then updated to conditionally render the "no readme" fallback message only after the fetch successfully completes with no HTML content, rather than showing the fallback unconditionally. This prevents the message from appearing whilst the README is still being fetched.

Possibly related PRs

• PR 1648: Modifies the same package page's readme fetching and template logic, addressing similar conditional rendering behaviour to avoid premature UI flicker during README loading.

Suggested reviewers

• danielroe

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description clearly describes the changes made to the README rendering logic and references the linked issue #2467.
Linked Issues check	✅ Passed	The code changes directly address issue #2467 by modifying the README rendering logic to check fetch status before displaying the no-README message.
Out of Scope Changes check	✅ Passed	All changes are focused on fixing the README loading state issue in the specified Vue component file, with no out-of-scope modifications.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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!

[serhalp]

could we add a loading state similar to this one? 🙏🏼

[serhalp]

🙏🏼 and while we're here, I think we aren't handling readme loading errors, are we? we could do something like this!

[serhalp]

🙌🏼 Thank you @akadotsh!