fix: more aggressive rate limit

[styfle]

Way too many requests coming from unknown clients. This will make sure clients identify themselves with a user-agent.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
packagephobia	✅ Ready (Inspect)	Visit Preview	Jun 20, 2024 11:06pm

[mrazauskas]

In few repos I have packagephobia badges added via badgens badge service: https://badgen.net/packagephobia

Recently most of them started appearing as 429. Just wondering, if this change can be the reason? Should they change something on their side?

EDIT. Very likely this is the cause. If I get this right, here is how they are sending requests: https://github.com/badgen/badgen.net/blob/b58e0de1762eb0de37ab6318fb06eee32bc55796/pages/api/packagephobia.ts#L19-L20

[amio]

What about making the API response a bit longer in cache?

Currently, this response (https://packagephobia.com/v2/api.json?p=eloc) has a cache-control header: public, max-age=30. I think we can make it public, s-maxage=60, max-age=30 to have the Vercel CDN cache it for an additional 60s.

[styfle]

Sounds good. But we also need badgen to set a user agent.

[amio]

429 issue fixed in badgen/badgen.net#673
preview https://badgennet-git-user-agent-badgen.vercel.app/#packagephobia/install/webpack

[mrazauskas]

Thanks! I just checked, all my badges are now fixed.