[Cloudflare Pages] The 'cache' field on 'RequestInitializerDict' is not implemented.

[samiy803]

On certain edge runtimes like Cloudflare (possibly others too), fetch() doesn't implement the cache field. As such, it produces an error:

// POST https://redacted.pages.dev/api/login
  "logs": [
    {
      "message": [
        {
          "code": "INTERNAL_ERROR",
          "message": "Internal error: The 'cache' field on 'RequestInitializerDict' is not implemented."
        }
      ],
      "level": "error",
      "timestamp": 1715189441063
    }
  ],

See: cloudflare/workerd#698

[samiy803]

Temporarily, can we add the feature to pass a custom fetch() function? Similar to: cloudflare/workerd#698 (comment)

[tstpierre]

Linking this PR thats in flight by James for next-on-pages cloudflare/next-on-pages#771

[awinogrodzki]

Hey!

Thanks for reporting @samiy803.

I've released a fix/workaround in [email protected]

More details about 1.5 can be found in #186

Could you test it and let me know if it works?

[awinogrodzki]

I will close the issue now, as 1.5 version has been released and cache: no-store is no longer passed to fetch method

[asaroukou]

Hi @awinogrodzki, I have a question about this update. Does it revert the changes required for this issue to be fixed #159. We didn't bumped the lib to the last version yet 😄.

[awinogrodzki]

Hey @asaroukou,

Yes, I've described the issue in this PR: #187

This PR removes the usages of cache fetch option

Due to above, it's recommended to update Next.js to v14 along with the upgrade to [email protected] to avoid caching issues

You need to update Next.js to version 14 before updating next-firebase-auth-edge to 1.5

[asaroukou]

You need to update Next.js to version 14 before updating next-firebase-auth-edge to 1.5

Ok so if I understand correctly the caching issue was only related to next 13. Since we already have the 14.x installed it should be fine to bump the lib to his last version.

[awinogrodzki]

Ok so if I understand correctly the caching issue was only related to next 13. Since we already have the 14.x installed it should be fine to bump the lib to his last version.

yes, exactly. The issue you faced in #159 was no longer reproducible in Next.js 14