Post

I'm asking because I'm building an alternative to npmjs.com, including the admin ui piece I have a working mvp, although of course it's very 🚧 if this is something you'd like to contribute to, and you've experienced any of these pain points, let me know - always more fun to build together! 🙏

🙋‍♂️ so ... for reasons: I would love to know people's frustrations with: - the current npmjs.com - admin user flows on npm web ui (and cli, locally) 🙏

Personally I'd be very conflicted here. I'm not sure further fracturing the ecosystem is a good idea. IMO we should either support JSR and the Deno team's efforts or we should improve npm as it exists. I feel like adding a _third_ variant (even if just a wrapper) is confusing.

To me this is one of the great challenges in the current JS ecosystem. There's a ton of energy and diversity, which is wonderful and means innovation/flexibility. But also folks don't seem to want to focus on aligning on solutions and improving those, roses and thorns.

Is there something specific JSR doesn't improve over the existing `npmjs.com` that your alternative would? Would it be more effective to contribute that to JSR directly and collaborate there?

Ah, I see! I guess there's no harm in that then. Still wish either JSR was more widely adopted or Microsoft would invest more in improving npm / npmjs.com. But if neither of those is going to happen it would be preferable to not get flashbanged when I open npmjs in the middle of the night.

0 reposts2 likes

No replies yet.