I maintain a monorepo. 22 packages. Every time I release, npm sends me 22 emails.
"Successfully published @scope/package-a"
"Successfully published @scope/package-b"
Twenty-two times. Every release. I release weekly. That's 88 emails a month that all say the same thing.
There's no opt-out. No digest option. No frequency control. Nothing.
I checked the npm feedback repository. People have been asking for this since 2018. Seven years of "please add a checkbox to disable these emails" or "can we get a digest option?" — all ignored. Then in 2024, npm archived the feedback repo entirely. Feature requests closed, problem unsolved.
So I built npmdigest.com.
The setup is simple:
That's it. Instead of 22 emails per release, you get one digest with everything grouped by package scope. It includes the publishing metadata too — OIDC info, token details, IP addresses — so you can still catch if something looks off.
Email infrastructure costs money. Running servers costs money. I could have made it free with ads or by harvesting data, but I hate both of those things. So it's €4.95/month with a 14-day free trial, no credit card required.
The billing model is postpaid — you get invoiced at the end of each month based on actual usage. If you forwarded emails that month, you pay. If you didn't, you don't. No upfront commitment, no "forgot to cancel" charges, no paying for months where you're on vacation or between projects.
Most SaaS tools charge you whether you use them or not. That felt wrong for something this simple. You're solving a problem npm created — you shouldn't also be locked into a subscription you have to remember to pause.
I mean that. npm could add a single checkbox tomorrow and this service would be obsolete. I'd be happy about it. The /why page on the site has the full history of ignored feature requests if you want to feel the frustration yourself.
But until npm decides their users' inboxes matter, npmdigest.com is here.