Avatar
MichaelJ 1y ago

Is anyone else getting a 404 on the NDK NPM registry page? https://www.npmjs.com/package/@nostr-dev-kit/ndk

nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft

Reply to this note

Please Login to reply.

Discussion

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

decentralized protocol writing code and publishing it to centralized shitty registry

why are you even using npm or cargo? you dumb

fucking

morons

Avatar
ChipTuner 1y ago

It's really easy to host tar-balls over http, or even git repos, for npm projects, that's what I do for my frontend libraries.

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

git hosting over http is not difficult

what's annoying is git push over http

Avatar
MichaelJ 1y ago

Update: it appears this is a general NPM outage.

https://downdetector.com/status/npm/

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

yeah, centralized registry, fuck you for using it

Avatar
ChipTuner 1y ago

You could always use the github repository instead.

Avatar
MichaelJ 1y ago

I'd have to figure out how to set that up with npm. It should be able to search multiple registries, but I'm not sure if it can handle GitHub as a registry.

And npm isn't building from source like we'd do with CMake.

Avatar
ChipTuner 1y ago

npm was made to reference soure packages. I reference my internal git repo all the time. There is no building its just all source typescript.

Avatar
MichaelJ 1y ago

I'll have to give that a shot!