The problem npm won't fix

One release, 22 emails.
All identical. All yours.

You maintain a monorepo. You publish a release. npm sends you 22 "Successfully published" notifications. No digest option. No frequency control. No way to opt out.

Stop the flood

14-day free trial · No credit card · Cancel anytime

We asked npm. Here's what they said.

N
npm-staffStaff
June 2021

"We are discussing features that will allow you to apply preferences... but this work is not currently on the roadmap."

→ github.com/npm/feedback/discussions/424
88+
upvotes on original issue
9
downvotes on that response
2024
feedback repo archived

So we built it.

Or learn how to filter npm emails yourself

Before & After

Your inbox, liberated

✕ Your inbox now
@acme/core@2.0.0 published
@acme/utils@2.0.0 published
@acme/cli@2.0.0 published
@acme/config@2.0.0 published
@acme/sdk@2.0.0 published
... 17 more
✕Hundreds of identical notifications
✕Important emails buried
✕No way to disable
✓ With npmDigest
Your Weekly npmDigest
22 updates across 1 scope
• @acme/* — 22 updates
Publishing metadata included
✓One email, all updates
✓Daily, weekly, or monthly
✓Actually useful

<3 minutes. Then forget about it.

Set up once, never think about npm email again

1

Sign up

Get your unique forwarding address

30 seconds

2

Set a filter

Forward npm emails to us. One filter, done forever.

2 minutes

3

Receive digests

Daily, weekly, or monthly — your choice

Forever

Simple pricing

One plan. Everything included. No limits.

npmDigest

€4.95/mo

14-day free trial · No credit card required

  • ✓Daily, weekly, or monthly digests
  • ✓Unlimited packages
  • ✓Grouped by scope (@org/*)
  • ✓Publishing metadata (OIDC, token, IP)
  • ✓Timezone-aware delivery
  • ✓Email support
Start free trial

No emails forwarded = no charge. You only pay for months you actually use it.

npm won't fix this.We did.

Start free trial