Just published my first package to the @github package repository: https://github.com/getify?tab=packages …
If all goes well, I'm going to (very slowly) be moving all my package publishing over there, away from npm.
-
Show this thread
-
I don't get what is the difference how you publish it – it is still available through https://www.npmjs.com/package/@getify/revocable-queue … or did you need to publish to NPM separately?
1 reply 0 retweets 0 likes -
I published to npm separately, mostly to reserve the name, but also as part of slowly changing over, will try to keep dual publishing (if possible).
2 replies 0 retweets 0 likes -
Yikes. No source of truth. This is bound to be a disaster. The only way I see this working is if package.json format starts automatically adding registry info along with dependency name/ version.
1 reply 0 retweets 0 likes -
single source of truth also means a registry is single point of failure and unchecked monopoly.
2 replies 0 retweets 0 likes
Let Linux Foundation acquire it. It would be only natural given that NPM is an integral part of Node.js ecosystem.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.