Alternative to the cache: no-cache in fetchClient

[n3oney]

Hi, 04034e24787cf454cad662f77b9901de9de9cf8c has introduced using the cache: "no-cache" option when making fetch requests. This however, is unsupported by Cloudflare's Workers and Pages, and unfortunately isn't silently ignored, but throws an error. Is it possible to have an option to disable that parameter, or some alternate solution bypassing it?

It currently causes this error: Error: The 'cache' field on 'RequestInitializerDict' is not implemented.

Which is gone by downgrading to 1.0.0-rc.3, which didn't have that commit in.

See https://github.com/cloudflare/workerd/issues/698#issuecomment-2053681304

[bkniffler]

Please... our logs have been silently failing due to this for several weeks. Maybe making the fetch function over writable would help with these kind of issues.

[multiplehats]

Yup same issue here

[thesollyz]

Have been waiting for Cloudflare to address this issue in https://github.com/cloudflare/workerd/issues/698#issuecomment-2053681304 but there haven't been any updates for a while.

The reason I added this cache parameter is to prevent frameworks like Next.js from caching the requests. Will have to think about a different solution

[SlexAxton]

Seems like https://github.com/axiomhq/axiom-js/pull/249 probably fixed this?

[thesollyz]

yes, version 1.3.1 was shipped with no-store.