Because they wanted to and Claude didn't tell them not to. Why even ask questions like this at this point.

I almost never use npmjs.com.

When I do it’s just to click on the repo link.

npmjs.com search input doesn't even have proper throttling/debounce. If you type fast, there is a high chance that you get result of the partial input that you entered than the complete one. Ideally they should discard the response for the old partial search if there is a new one.

https://github.com/npmx-dev/npmx.dev has a comparison

It is really annoying if you have a package that is relatively new to the platform, and you type in the exact package name, that package is not reliably the first result.

Minor edge case, but infuriating if you want to check your own packages quickly (without needing to navigate menu > packages > YOUR_PACKAGE).

Still agree with you though, who is npmx actually for?

npmjs search is very slow

A valid use case I can think of is if npmjs.com is blackholed by your company to prevent supply chain attacks

It sparks more joy than the old one and buddy, that's for frelling enough damn it. Whinge out!

Awful comment. Your comment is bad and should be ashamed.

Use it and disagree! Tell me it in fact does not spark more joy! This just seems pretty clear, ya'll.

It's just generally vastly nicer. I love that file exploration of packages doesn't feel like a last afterthought before leaving the solar system forever.

Cynically, if you can attract a representative sample, you could aggregate and sell analytics data.

Another could be to have an "alternatives" section based on semantic similarity and / or some other features that have signal.