Skip to content

feat: add suggested packages to comparison package selector#873

Draft
thasmo wants to merge 1 commit intonpmx-dev:mainfrom
thasmo:suggested-packages
Draft

feat: add suggested packages to comparison package selector#873
thasmo wants to merge 1 commit intonpmx-dev:mainfrom
thasmo:suggested-packages

Conversation

@thasmo
Copy link
Contributor

@thasmo thasmo commented Feb 3, 2026

Just a demonstration for "suggested" packages.

@vercel
Copy link

vercel bot commented Feb 3, 2026

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

Project Deployment Actions Updated (UTC)
npmx.dev Ready Ready Preview, Comment Feb 3, 2026 8:12pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
docs.npmx.dev Ignored Ignored Preview Feb 3, 2026 8:12pm
npmx-lunaria Ignored Ignored Feb 3, 2026 8:12pm

Request Review

Copy link
Contributor

@wojtekmaj wojtekmaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would have been really cool. I think we could gather some analytics data from /compare to compile a list of "often compared with..." that we then could use to power such functionality. It's a multi-step enhancement though :(

@thasmo
Copy link
Contributor Author

thasmo commented Feb 3, 2026

I think we could gather some analytics data from /compare to compile a list of "often compared with..."

Yep, that would work. I hoped there's some API, but I can't find any. Also using keyword search is not an option as keyword quality is quite low I'd say. But gathering "often compared with" data would work.

@serhalp
Copy link
Collaborator

serhalp commented Feb 3, 2026

FYI I have this over here: #801

@thasmo
Copy link
Contributor Author

thasmo commented Feb 3, 2026

@serhalp, that's awesome, and I think it's perfect for this type of information. But I also think the "suggested" or "often compared with" packages are different, as in you would compare e.g. next with nuxt or alpine with jquery but you wouldn't want to replace one with the other necessarily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants