-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
fix(cookies): Update Undici to 5.20 and fix cookies behaviour #6323
Conversation
🦋 Changeset detectedLatest commit: 7713080 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
// them. There are non-standard ways to do it, and node-fetch gives us headers.raw() | ||
// See https://github.com/whatwg/fetch/issues/973 for discussion | ||
if (response.headers.has('set-cookie')) { | ||
if ('raw' in response.headers) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Old left over from node-fetch. When everything is gonna be updated to use getSetCookie
, we'll also be able to remove the whole splitCookiesString
thing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Great to be able to remove the old hacks. Looks like this would need a changeset too.
* fix(cookies): Update Undici to 5.20 and fix cookies behaviour * chore: changeset
* fix(cookies): Update Undici to 5.20 and fix cookies behaviour * chore: changeset
* fix(cookies): Update Undici to 5.20 and fix cookies behaviour * chore: changeset
Changes
Now that Undici released 5.20, we can upgrade again. This fix the
npm audit
warningTesting
Tests will pass!
Docs
N/A