-
Notifications
You must be signed in to change notification settings - Fork 143
Error when deploying to cloudflare workers #340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For anyone facing the same problem as me, the only alternative I could find was to downgrade at
|
In my case I had the error while trying to acces to What finally worked for me was to downgrade the auth-js package adding this line in the package.json file: If it's still not working try to delete .nuxt and node_modules and package-lock.json file. Then run This was the way to make it work for me. Hope it helps. |
This also causes issues with route protection on SSR, but it works fine on client only with Cloudflare pages.
Fixed this for me also. |
Do you have any idea to work around this problem without downgrading the dependency? |
This PR seems to fix the problem: supabase/auth-js#886 They upgrade the version of By upgrading |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Version
@nuxtjs/supabase: v1.2.0
nuxt: 3.8.1
Steps to reproduce
When using the
useSupabaseUser()
function on a CloudFlare Worker it returns the following error:The problem started to occur in the new version
v1.2.0
and from what I investigated the problem was due to an update to the supabase library as reported here. The whole problem is that the fetch used by the CloudFlare Worker does not support the cache parameter as described here.In the case of
supabase-js
, the workaround is to remove the fetch cache header as described here.However, as
@nuxtjs/supabase
uses theclientOptions
property innuxt.config.ts
, the functions defined there do not work at run time. In other words, the code below does not work:So, this came to me with a question.. The way the library is currently implemented, how can we pass a custom fetch implementation, which is a feature of supabase-js?
The text was updated successfully, but these errors were encountered: