Live data from Hacker News

NPMX – a fast, modern browser for the NPM registry

npmx.dev

71–76 of 76 posts

Re: NPMX – a fast, modern browser for the NPM registry

#71
post #3

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.

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

Check who the maintainers are. This is highly unlikely. If you want to know what Daniel thinks of Claude read https://roe.dev/blog/the-golden-thread

Re: NPMX – a fast, modern browser for the NPM registry

#72

npmx maintainer here! a few answers to questions i see: we haven’t launched yet! we’re building openly but aiming for march 3. as is par for the course, hn gets the scoop. i made the first commit two weeks ago, so it’s very new. but we’ve had 900+ PRs and 170+ contributors in the last fortnight… because this is something we care about. having said that, i’m taking notes about what is and isn’t intuitive npmjs remains…

Best of luck, hope it goes well!

Re: NPMX – a fast, modern browser for the NPM registry

#75

Earlier quoted context omitted.

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

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.

> In the age of LLMs I think we are going to see a Cambrian explosion of software.

From Wikipedia: "Application software _runs_ [1] on top of the operating system"

[1] emphasis mine.

Re: NPMX – a fast, modern browser for the NPM registry

#76

Earlier quoted context omitted.

Life-changing: ghub.io/ No idea where I found this but I’ve been using for many, many years.

How's it life changing though? You have to know the package name already to do that. And if you're sitting on npmjs looking at the package already, then you're one click away from Github. Furthermore... I don't host my packages on Github :-) Don't think that even works for mine.

When you see an unknown package in a package.json, you can go straight to the source - no search or visiting npm.com
Post reply on HN