-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[node] swap undici.fetch
for undici.request
in serverless-handler.mts
#10767
Conversation
🦋 Changeset detectedLatest commit: b7da26d The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
7619a33
to
dfa22fe
Compare
Co-authored-by: Hugo Martinez <contact@hmartinez.fr>
dfa22fe
to
35ff6df
Compare
@Ethan-Arrowood I think that error in In fact, the Si I've made this PR : vercel/edge-runtime#672 |
…ss-function-dev-proxy
…ss-function-dev-proxy
…ss-function-dev-proxy
…ss-function-dev-proxy
Some tests were failing to do log incident yesterday. re-running now |
Co-authored-by: Sean Massa <EndangeredMassa@gmail.com>
b7da26d
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## vercel@32.5.3 ### Patch Changes - Handle `TooManyProjects` error in places where projects are created ([#10807](#10807)) - Updated dependencies \[[`89c1e0323`](89c1e03), [`fd29b966d`](fd29b96)]: - @vercel/node@3.0.9 - @vercel/next@4.0.14 ## @vercel/next@4.0.14 ### Patch Changes - Fixed headers for static routes when PPR is enabled ([#10808](#10808)) ## @vercel/node@3.0.9 ### Patch Changes - Replace usage of `fetch` with `undici.request` ([#10767](#10767)) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
it's unnecessary after switched from node-fetch to undici: #10767
In a recent undici update, setting the
host
header for fetch requests became invalid (nodejs/undici#2322).We relied on this in order to proxy serverless dev server requests via
@vercel/node
.This PR replaces the usage of
undici.fetch
withundici.request
.It is blocked by an
undici
type change: nodejs/undici#2373