If you call setCookie twice, it will only set the last cookie

[JosephCarrington]

export function setCookie(ctx = {}, name, value, options = {}) {
  if (ctx && ctx.res) {
    ctx.res.setHeader('Set-Cookie', cookie.serialize(name, value, options))
  }

  if (process.browser) {
    document.cookie = cookie.serialize(name, value, options)
  }

  return {}
}

[dougwilson]

I'm not sure how the code in this module would be able to fix that issue. The only thing it looks like you are calling from this module is the cookie.serialize function? Any thoughts on what changes we can make / would you be willing to make a pull request?

[JosephCarrington]

Well specifically

getInitialProps({ctx}) {
  setCookie(ctx, 'foo', 'bar');
  setCookie(ctx, 'bar', 'baz');
}

will only set the bar cookie

[JosephCarrington]

If I come up with a solution I'll happily make a PR

[dougwilson]

Yea, but I mean are you sure the bug is in this lib or your code you posted? All this module is doing in your code is producing a string.

[JosephCarrington]

So how would you go about setting two separate cookies?

[dougwilson]

So I'm a bit unfamiliar with what the ctx.res.setHeader comes from. Each Set-Cookie is a separate header. Does that API allow setting the same header name with multiple values? Or is there a different API to use?

[JosephCarrington]

OMG I'm so sorry. This was supposed to be on the 'nookies' github. Sorry sorry sorry

[dougwilson]

Oh, I see now. What you pasted above was just the code from the nookies source 😆

https://github.com/maticzav/nookies/blob/master/src/index.js#L16-L26

It's no problem at all!