You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node is getting fetch as a default global, but it's not there yet:
(node:7796) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
When Node.js LTS stops issuing that warning we may be able to switch to the webpack-ready browser.js (forthcoming) to being the main for both.
The API would be kept largely the same, but at the very least there will be subtleties that require a breaking change major version bump, so perhaps we'll drop a few old features too.
Why not abandon request in favor of fetch?
In many cases that should be done, but there are a few things - such as handling opts.auth- that require a small amount of utility code.
Node is getting
fetch
as a default global, but it's not there yet:When Node.js LTS stops issuing that warning we may be able to switch to the webpack-ready
browser.js
(forthcoming) to being the main for both.The API would be kept largely the same, but at the very least there will be subtleties that require a breaking change major version bump, so perhaps we'll drop a few old features too.
Why not abandon
request
in favor offetch
?In many cases that should be done, but there are a few things - such as handling
opts.auth
- that require a small amount of utility code.Node's
fetch
vs WHATWGfetch
See https://github.com/nodejs/undici/#specification-compliance.
In summary:
Set-Cookie
,Cookie
andUser-Agent
The text was updated successfully, but these errors were encountered: