atpkgs fact: there has never been a supply chain attack on atpkgs
atpkgs 📦
@atpkgs.easrng.net
A decentralized package registry for JavaScript and TypeScript, built on @atproto.com
minor atpkgs update: fixed an issue where pnpm was complaining about mismatches between the registry and the tarball's package.json
With this new update, the frontend for pdsmoover.com is fully powered by the new node library. With this library, you can now easily create your own UI for Atproto migrations, without worrying about migration logic Can find it on npm as well as @atpkgs.easrng.net atpkgs.easrng.net/@baileytowns...
npmjs.com
btw whenever I say npx I really mean "pnpx, npx, yarn dlx, or bunx (pick your favorite)"
you can publish too! run `npx atpkgs publish` in your package's directory to get started.
okay I published something real (my url/encoding/etc. implementation) to atpkgs.easrng.net
should atpkgs also set up your package manager for jsr dependencies or is that out of scope
Should it be possible to change a package name? You can already change your handle, which changes the scope.
200+ follows in one day? wow I was not expecting this much excitement! I'll have something out soon :)