TypeError: e.getSetCookie is not a function

[grzegorzpokorski]

Link to the code that reproduces this issue

https://github.com/grzegorzpokorski/nextjs-getsetcookie-error

To Reproduce

1. clone repo
2. pnpm i
3. pnpm dev
4. open localhost:3000 in browser
5. should occur error

Current vs. Expected behavior

error should not occur

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
Binaries:
  Node: 18.11.0
  npm: 8.19.2
  Yarn: 1.22.19
  pnpm: 8.9.2
Relevant Packages:
  next: 13.5.6-canary.2
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Additional context

No response

[ze-kel]

Just wanted to open this. Breaked lucia-auth in my project.

I also digged a bit more and discovered that this issue is not preset when using Node v16, while being present on Node Stable(v19.3.0).

Codesandbox with it working on Node 16.

[huozhi]

I can repro this with node 18.11, you can upgrade your nodejs version 18.16 it will fix the problem

[zfreiter]

I think I have a similar issue -> TypeError: responseHeaders.getSetCookie is not a function.
Today was my first time creating a Nextjs app. I have Node v18.18.2 and I had the most current NextJS version for the basic start for a NextJS application. When I change the NextJS to version 13.5.4 the error goes away.

[grzegorzpokorski]

@huozhi you have right! Upgrading Node.js to 18.16.1 resolved issue. App also successfully builds on Vercel ❤

[jawkhan]

I experienced this error after upgrading NextJS to 13.5.5. Upgrading to the latest version of node worked for me. I had version 19.1.0 and upgraded to version 21.0.0.

I used node version manager (nvm) and ran the following command to get the latest version of node installed:
nvm install node

You can follow these instructions to install nvm:
https://www.freecodecamp.org/news/node-version-manager-nvm-install-guide/

[abdolrhman]

upgrade fix the issue, use latest node --v v18.18.2

[MuhammadAli-123]

Yes, After Upgrading the Node Version to Latest will solve this problem.

[brob]

I've tried Node versions 18.18.2, 19.0.0, 21.0.0 and have this issue with both draftMode().enable() and cookies().set(). Are there other workarounds?

[huozhi]

We patched a fix https://github.com/vercel/next.js/releases/tag/v13.5.6, please upgrade to the new version

[8ctopotamus]

Next 13.5.6 worked for me! Running Node 18.12.

[goudete]

I can repro this with node 18.11, you can upgrade your nodejs version 18.16 it will fix the problem

This worked for me. THANK YOU!

[Matdweb]

It also worked for me! And I am running node 20.9.0!
But It would be great to put this in the documentation because it took me a while to get to this Issue and I had no idea 😢

[Matdweb]

It also worked for me! And I am running node 20.9.0! But It would be great to put this in the documentation because it took me a while to get to this Issue and I had no idea 😢

I actually encountered issues with API routes in Next.js 13, and it was quite challenging because they didn't work at all, and I had no idea why.
But with this is, it is finally resolved 😄

[huozhi]

If you're running 13.5.6, the allowed engine versions of node.js should be fine

#56947 (comment)