3 ms·
npm process to setup OIDC is way too frustrating. There is just so much friction. You need the package to first exists in the registry, meaning you have to firs
by dgellow 7mo ago
npm process to setup OIDC is way too frustrating. There is just so much friction. You need the package to first exists in the registry, meaning you have to first create an API token and push something. And only then can you enable OIDC for that specific package. After adding the repo + workflow names, you have to save. Then finally toggle the “only allow OIDC publishing”.
Before each action you need to enter your 2fa code.
I got so frustrated with npm end of last year that I wrote a whole guide covering that issue: https://npmdigest.com/guides/npm-trusted-publishing https://npmdigest.com/guides/npm-trusted-publishing
- mcintyre1994 7mo agoYou’re right, but a colleague recently showed me this CLI for it: https://docs.npmjs.com/cli/v11/commands/npm-trust https://docs.npmjs.com/cli/v11/commands/npm-trust Still needs to be published first, but looks like it automates all the annoying UI things you mentioned.
- dgellow 7mo agoOh that’s neat! Thank you for sharing!