-
Notifications
You must be signed in to change notification settings - Fork 19
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
TypeError: headers.getSetCookie is not a function
#109
Comments
I am having the same problem. It also occurs with loaders that only It is also reported in the issue of remix-run Perhaps I should try to use nativeFetch on runtime, but since it is vercelPreset and not a custom server, I don't know what to do. |
I'm getting this error too. I tried to use node 20 if it solves the issue, but it's the same. |
It would be nice to be able to control it externally somehow so that the following part called after invoking serverless functions becomes
|
So I've found a workaround using Object.defineProperty to set the globals and prevent changes to them, and by monkey-patching in an API that Here's the gist https://gist.github.com/michalmo/d62e9a2e001183ec1df1bcac74980abb. I call the Hope this helps somebody :) |
Thank you sooo much!! You saved me a couple of headaches |
@brophdawg11 Do you have an update regarding these or how can we help? Seems that this is an issue on the Vercel Side of things since locally is running ok |
If Vercel needs a polyfill and doesn't have a |
Although the
|
Hi! I'm testing the new Single Fetch behaviour in Remix, but I'm having trouble with
headers.getSetCookie
which seemingly isn't present when running on Vercel for some reason.As noted in the changelog, I've enabled
nativeFetch
ininstallGlobals
but the TypeError is still present. The error I get is this:To reproduce, simply create a new Remix-project with
npx create-remix@latest
and put this in the_index.tsx
-file:`vite.config.ts`
Then deploy to vercel.
Even without the new SingleFetch behaviour, using
headers.getSetCookie
still doesn't work. This can be reproduced by removingunstable_singleFetch
fromfuture
invite.config.ts
, and changing the_index.tsx
-file to this:Any help appreciated!
The text was updated successfully, but these errors were encountered: