Why I Built pubm: One CLI to Publish to npm, JSR, and Beyond
It was a Friday afternoon. npm publish finished clean. Then I remembered I hadn't updated jsr.json. Ran npx jsr publish. Auth error, my JSR token had expired. So I refreshed it, ran again, and the ...

Source: DEV Community
It was a Friday afternoon. npm publish finished clean. Then I remembered I hadn't updated jsr.json. Ran npx jsr publish. Auth error, my JSR token had expired. So I refreshed it, ran again, and the version numbers between npm and JSR were now out of sync because I'd forgotten to bump jsr.json before the first publish. That was the moment I started writing pubm. I began the project in 2024, got it to a working prototype, then life happened and it sat untouched for months. I picked it back up with Claude as a coding partner and brought it to completion. The architecture decisions and test coverage were mine to own (I wasn't going to hand that off), but having an AI pair helped me push through the implementation grind that had stalled the project the first time around. The Problem: Multi-Registry Publishing is a Manual Mess When JSR entered public beta in March 2024, it brought something genuinely useful: a TypeScript-first registry backed by Deno, with a governance board that includes Eva