fix(ui): remove install package command version for latest

[bluwy]

🔗 Linked issue

n/a

🧭 Context

#1969 made a change that caused the version to show up in the install command, even if the package link does not have a version, e.g. https://main.npmx.dev/package/vite

The version shouldn't be showed in this case

📚 Description

This PR returns it to like before, http://localhost:3000/package/vite

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ready	Preview, Comment	Mar 22, 2026 3:53am
npmx.dev	Ready	Preview, Comment	Mar 22, 2026 3:53am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		Mar 22, 2026 3:53am

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

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: bf0dbc10-9ff3-4784-821c-1c55b8fa3db0

📥 Commits

Reviewing files that changed from the base of the PR and between 9efc03a and f052b51.

📒 Files selected for processing (1)

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

---

📝 Walkthrough

Walkthrough

Changed the TerminalInstall component binding in app/pages/package/[[org]]/[name].vue: the requested-version prop now receives resolvedVersion only when requestedVersion is present and not "latest"; otherwise it receives null. This alters control flow only when there is no explicit non-latestrequestedVersion; behaviour is unchanged for explicit non-latest requests. Change size: +3 / -1.

Possibly related PRs

• npmx-dev/npmx.dev PR 1958: Modifies the same prop bindings in app/pages/package/[[org]]/[name].vue, changing which version value is passed to TerminalInstall.

Suggested labels

help wanted

Suggested reviewers

• danielroe
• 43081j

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description clearly explains the issue (version showing in install command when it shouldn't) and directly relates to the changeset which conditionally passes the version only when appropriate.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch install-version-latest

---

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

Tip

CodeRabbit can generate a title for your PR based on the changes.

Add @coderabbitai placeholder anywhere in the title of your PR and CodeRabbit will replace it with a title based on the changes in the PR. You can change the placeholder by changing the reviews.auto_title_placeholder setting.

[alex-key]

Since you still could click on the latest version semver and url would be changed (and requestedVersion added) I would improve logic to omit this prop in case resolvedVersion is the latest. But it's up to you

[bluwy]

Done. Personally I'd show the tag too, if it's beta for example so it's pkg@beta and not pkg@1.2.3, but I'd like to get some form of this fix out first so it doesn't show a pinned version install.