fix: edge fetch no cache invalid (#1012)

## Summary of change

This PR fixes an issue with `fetch` calls throwing in Cloudflare workers due to the newly added `cache` support from CF where only `no-store` is supported.

## Related issues

## Test Plan

All tests should pass including deployment on Cloudflare Workers

## Documentation changes

(If relevant, please create a PR in our [docs repo](https://github.com/supertokens/docs), or create a checklist here highlighting the necessary changes)

## Checklist for important updates

-   [x] Changelog has been updated
-   [ ] `coreDriverInterfaceSupported.json` file has been updated (if needed)
    -   Along with the associated array in `lib/ts/version.ts`
-   [ ] `frontendDriverInterfaceSupported.json` file has been updated (if needed)
-   [ ] Changes to the version if needed
    -   In `package.json`
    -   In `package-lock.json`
    -   In `lib/ts/version.ts`
-   [x] Had run `npm run build-pretty`
-   [x] Had installed and ran the pre-commit hook
-   [ ] If new thirdparty provider is added,
    -   [ ] update switch statement in `recipe/thirdparty/providers/configUtils.ts` file, `createProvider` function.
    -   [ ] add an icon on the user management dashboard.
-   [x] Issue this PR against the latest non released version branch.
    -   To know which one it is, run find the latest released tag (`git tag`) in the format `vX.Y.Z`, and then find the latest branch (`git branch --all`) whose `X.Y` is greater than the latest released tag.
    -   If no such branch exists, then create one from the latest released branch.
-   [ ] If have added a new web framework, update the `add-ts-no-check.js` file to include that
-   [ ] If added a new recipe / api interface, then make sure that the implementation of it uses NON arrow functions only (like `someFunc: function () {..}`).
-   [ ] If added a new recipe, then make sure to expose it inside the recipe folder present in the root of this repo. We also need to expose its types.
-   [ ] If added a new entry point, then make sure that it is importable by adding it to the `exports` in `package.json`

## Remaining TODOs for this PR

Author: porcellus

CHANGELOG.md

@@ -25,6 +25,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 -   The `User` class now has a `fromApi` function to normalize the user object returned from the API.
 -   Refactors querier to use dynamic request body and response body types inference.
 -   Refactor internal network calls made with querier to use the new dynamic types.
+-   Fixes an issue with fetch not supporting `cache: no-cache` in Cloudflare Workers.
 
 ## [22.1.0] - 2025-04-04
 

lib/build/utils.js

@@ -17,38 +17,46 @@ export const doFetch: typeof fetch = async (input: RequestInfo | URL, init?: Req
     if (init === undefined) {
         ProcessState.getInstance().addState(PROCESS_STATE.ADDING_NO_CACHE_HEADER_IN_FETCH);
         init = {
-            cache: "no-cache",
+            cache: "no-store",
             redirect: "manual",
         };
     } else {
         if (init.cache === undefined) {
             ProcessState.getInstance().addState(PROCESS_STATE.ADDING_NO_CACHE_HEADER_IN_FETCH);
-            init.cache = "no-cache";
+            init.cache = "no-store";
             init.redirect = "manual";
         }
     }
+
+    // Remove the cache field if the runtime is Cloudflare Workers
+    //
+    // CF Workers did not support the cache field at all until Nov, 2024
+    // when they added support for the `cache` field but it only supports
+    // `no-store`.
+    //
+    // The following check is to ensure that this doesn't error out in
+    // Cloudflare Workers where compatibility flag is set to an older version.
+    //
+    // Since there is no way for us to determine which compatibility flags are
+    // enabled, we are disabling the cache functionality for CF Workers altogether.
+    // Ref issue: https://github.com/cloudflare/workerd/issues/698
+    if (isRunningInCloudflareWorker()) {
+        delete init.cache;
+    }
+
     const fetchFunction = typeof fetch !== "undefined" ? fetch : crossFetch;
     try {
         return await fetchFunction(input, init);
     } catch (e) {
-        // Cloudflare Workers don't support the 'cache' field in RequestInit.
-        // To work around this, we delete the 'cache' field and retry the fetch if the error is due to the missing 'cache' field.
-        // Remove this workaround once the 'cache' field is supported.
-        // More info: https://github.com/cloudflare/workerd/issues/698
-        const unimplementedCacheError =
-            e &&
-            typeof e === "object" &&
-            "message" in e &&
-            e.message === "The 'cache' field on 'RequestInitializerDict' is not implemented.";
-        if (!unimplementedCacheError) throw e;
-
-        const newOpts = { ...init };
-        delete newOpts.cache;
-
-        return await fetchFunction(input, newOpts);
+        logDebugMessage("Error fetching: " + e);
+        throw e;
     }
 };
 
+function isRunningInCloudflareWorker() {
+    return typeof navigator !== "undefined" && navigator.userAgent === "Cloudflare-Workers";
+}
+
 export function getLargestVersionFromIntersection(v1: string[], v2: string[]): string | undefined {
     let intersection = v1.filter((value) => v2.indexOf(value) !== -1);
     if (intersection.length === 0) {