But why?

npmjs.com is not slow and not something I need to interact with very often.

And npmjs.com is still the authority when it comes to publishing packages, no? So I'd still have to use it.

xhcuvuvyc 6 hours ago | parent | next [-]

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

	▲	indemnity 5 hours ago \| parent \| next [-]
		In the age of LLMs I think we are going to see a Cambrian explosion of software. Me personally, I’m writing tools for myself wouldn’t have bothered with before due the the time investment needed.
	▲	port11 3 hours ago \| parent \| prev \| next [-]
		The prolific inventor’s dilemma. But to be fair developers have been making whatever they want since the beginning. Sometimes there doesn’t have to be a ‘why?’.
	▲	isodev 3 hours ago \| parent \| prev [-]
		Haha this. I understand the appeal of "but I can probably roll my own" and "Oh that's a good idea, let's jump into coding" but pre-vibe bots, the effort required would make folks stop and think before jumping into it - is it really a good idea? should I do it just because I can? what problem is it really solving? Who will use this? etc.

▲

riedel 2 hours ago | parent | prev | next [-]

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

▲

pier25 7 hours ago | parent | prev | next [-]

I almost never use npmjs.com.

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

	▲	tmvnty an hour ago \| parent [-]
		I just do ghub.io/<package-name>

▲

brycelarkin 8 hours ago | parent | prev | next [-]

npmjs search is very slow

▲

DeepYogurt 8 hours ago | parent | next [-]

how often does anyone use it though?

▲

65 8 hours ago | parent | prev [-]

I mean are we really arguing over milliseconds here? I have never in my life had the thought "NPM search is too slow, I need a faster solution"

I have had the thought "NPM search sorted by downloads this week is giving me irrelevant packages" - but I'm not sure this tool solves that.

▲

blue_pants 6 hours ago | parent | next [-]

It can load for a couple of seconds (!) for me

▲

skydhash 8 hours ago | parent | prev [-]

My only pain point, that I solved with a few lines of elisp, was to go to npmjs, to find the repo link for my dependencies. What's in `node_modules` may be compiled to an inscrutable blob and it's rare to find good library docs.

	▲	ricardobeat 3 hours ago \| parent [-]
		Life-changing: ghub.io/<package> No idea where I found this but I’ve been using for many, many years.

▲

nickradford 7 hours ago | parent | prev | next [-]

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?

	▲	ireadmevs 6 hours ago \| parent [-]
		Whenever I know the name of the package I want to see, I always type in the URL directly: npm.im/[package-name]

▲

jauntywundrkind 5 hours ago | parent | prev | next [-]

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.

▲

jasonjmcghee 7 hours ago | parent | prev [-]

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.