-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
chore: remove node-fetch
#55112
chore: remove node-fetch
#55112
Conversation
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
a6427e6
to
722bdef
Compare
Failing test suitesCommit: 4c889da
Expand output● experimental-https-server (provided certificate) › should successfully load the app in app dir
● experimental-https-server (provided certificate) › should successfully load the app in pages dir
Read more about building and testing Next.js in contributing.md.
Expand output● app-custom-routes › body › can handle handle a streaming request and streaming response
● app-custom-routes › body › can handle handle a streaming request and streaming response (edge)
● app-custom-routes › body › can read a streamed JSON encoded body
● app-custom-routes › body › can read a streamed JSON encoded body (edge)
Read more about building and testing Next.js in contributing.md.
Expand output● app-custom-routes › body › can handle handle a streaming request and streaming response
● app-custom-routes › body › can handle handle a streaming request and streaming response (edge)
● app-custom-routes › body › can read a streamed JSON encoded body
● app-custom-routes › body › can read a streamed JSON encoded body (edge)
Read more about building and testing Next.js in contributing.md.
Expand output● dev mode › should use correct data URL for root catch-all
● production mode › should use correct data URL for root catch-all
Read more about building and testing Next.js in contributing.md.
Expand output● next-image-proxy › should work with connection upgrade by removing it via filterReqHeaders()
Read more about building and testing Next.js in contributing.md.
Expand output● Dynamic Routing › dev mode › should handle only query on dynamic route
● Dynamic Routing › dev mode › should handle only hash on dynamic route
● Dynamic Routing › dev mode › should navigate to a dynamic page successfully interpolated
● Dynamic Routing › dev mode › should navigate to a dynamic page successfully interpolated with additional query values
● Dynamic Routing › dev mode › should navigate to a nested dynamic page successfully interpolated
● Dynamic Routing › dev mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (single interpolated)
● Dynamic Routing › dev mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (multi interpolated)
● Dynamic Routing › production mode › should handle only query on dynamic route
● Dynamic Routing › production mode › should handle only hash on dynamic route
● Dynamic Routing › production mode › should navigate to a dynamic page successfully interpolated
● Dynamic Routing › production mode › should navigate to a dynamic page successfully interpolated with additional query values
● Dynamic Routing › production mode › should navigate to a nested dynamic page successfully interpolated
● Dynamic Routing › production mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (single interpolated)
● Dynamic Routing › production mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (multi interpolated)
Read more about building and testing Next.js in contributing.md.
Expand output● Read-only source HMR › should detect changes to a page
● Read-only source HMR › should handle page deletion and subsequent recreation
Read more about building and testing Next.js in contributing.md.
Expand output● Production Usage › With basic usage › should allow etag header support
● Production Usage › With basic usage › should allow etag header support with getStaticProps
Read more about building and testing Next.js in contributing.md.
Expand output● ipc-forbidden-headers › should not error if expect header is included
● ipc-forbidden-headers › should not error on content-length: 0 if request shouldn't contain a payload
Read more about building and testing Next.js in contributing.md.
Expand output● Client Navigation › Rendering via HTTP › should should not contain scripts that are not js
Read more about building and testing Next.js in contributing.md. |
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
|
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
fde8cce
to
6b121a7
Compare
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
6b121a7
to
2ac2838
Compare
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
052d56a
to
475f11b
Compare
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
What?
Removing
node-fetch
in favorfetch
provided by the platform.NOTE: This is a cleanup in the repository,
next
stopped usingnode-fetch
a while ago already: #49061Why?
Node.js 16 is EOL and although we might support it a bit longer for an easier migration, this is a preparation for being able to drop any kind of polyfilling via
undici
(which Node.js itself uses too).Continues on #55105 to be able to use platform-only
fetch
everywhere, without polyfillsHow?
The main changes are fixing compatibility issues between
node-fetch
and undici/Fetch API spec. Here is a rough summary of the content of this PR:await res.buffer()
calls toBuffer.from(await res.text())
ReadableStream
(Web API) instead of Node.jsReadable
.Cache-Control
header in tests to correctly return 304 when necessary (Ref: fetch: cache headers are wronly added to conditional requests nodejs/undici#1930)node-fetch
Agent toundici
'sundici
can return relative URLs for redirects (Ref: the redirect handler does not correctly honor relative paths in the location header nodejs/undici#1521)