Reject cache.invalidate() when Cloudflare refuses the purge

[danielmlr]

Changes

• Workers Cache reports a refused purge, including one over the rate limit, as success: false in the result of cache.purge() (docs). The provider dropped that result, so cache.invalidate() resolved and the pages stayed cached with nothing logged. Workers Cache purges always use the Free-tier limit of 5 per minute per account, with a bucket of 25 (limits), which a site that purges on every content save can reach.
• The provider throws when success is false, with Cloudflare's errors as the error's cause, as invalidate() already does on Netlify when its purge request fails. Successful purges are unchanged. Callers that await invalidate() after a write start seeing rejections; EmDash is guarding its calls in fix(core): stop a failed cache purge from failing a saved write emdash-cms/emdash#3987.

Testing

• New test/units/cache-purge.test.ts covers the purge step with a stand-in cache object, since cloudflare:workers does not load in Node: an accepted purge passes the tags through and resolves, a refused one rejects with the returned errors as cause.

Docs

• None needed: the route caching guide does not describe what invalidate() does when a purge fails, for any provider.

[changeset-bot]

🦋 Changeset detected

Latest commit: 96e055f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@astrojs/cloudflare	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR