Closed M-Nasab closed 2 years ago
This could happen because fetch-cookie assumes you use node-fetch v2 and may fail if you aren't:
What fetch implementation are you using in what environment?
FWIW I've got this happening right now, using node-fetch
2.6.1. Replicated in both Firefox and Safari.
Hey! I just published v2.0.0 with improved support for various fetch
implementations!
headers.raw
was pretty specific to node-fetch but now fetch-cookie also supports any fetch
implementation compatible with the WHATWG Fetch standard API (as long as it exposes the set-cookie
header)
I get this error when i use this library: