POST request from middleware fails

[dferber90]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000
Binaries:
  Node: 17.4.0
  npm: 8.3.1
  Yarn: 1.22.19
  pnpm: 7.4.0
Relevant packages:
  next: 12.2.4-canary.2
  eslint-config-next: 12.2.3
  react: 18.2.0
  react-dom: 18.2.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

Fetch requests made from middleware fail but only if the request is a POST request with a request body.

Expected Behavior

The middleware should be able to make POST requests.

Link to reproduction

https://github.com/dferber90/nextjs-fetch-bug-reproduction

To Reproduce

1. Create a new Next.js project, eg pnpm create next-app --ts.

2. Add a middleware.ts file at the root with:

// middleware.ts
export const config = { matcher: "/" };

export async function middleware() {
  const text = await fetch("https://example.com", {
    method: "POST",
    body: "",
  }).catch((error) => {
    console.error(error);
    throw error;
  });

  console.log(text);
}

3. Visit http://localhost:3000

You will now see the red warning box.

Additionally, the middleware will have logged the error to the terminal:

// from: console.error(error)
{ [TypeError: fetch failed]
  cause: [TypeError: define_process_default.nextTick is not a function] }

// from: throw error
error - Error [TypeError]: fetch failed
    at Object.processResponse (evalmachine.<anonymous>:3033:34)
    at <unknown> (evalmachine.<anonymous>:3366:42)
    at <unknown> (node:internal/process/task_queues:141:7)
    at AsyncResource.runInAsyncScope (node:async_hooks:201:9)
    at AsyncResource.runMicrotask (node:internal/process/task_queues:138:8)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  middleware: true
}

[dferber90]

I debugged this a bit myself, maybe this is useful:

The console.error(error) output shows:

{ [TypeError: fetch failed]
  cause: [TypeError: define_process_default.nextTick is not a function] }

So define_process_default seems to be defined in

next.js/packages/next/compiled/@edge-runtime/primitives/fetch.js

Line 63 in 90ddd0d

var env, versions, define_process_default;

Note that the provided default has no nextTick function:

next.js/packages/next/compiled/@edge-runtime/primitives/fetch.js

Line 68 in 90ddd0d

define_process_default = { env, versions };

But nextTick is called 4 times in that file

next.js/packages/next/compiled/@edge-runtime/primitives/fetch.js

Line 6001 in 90ddd0d

define_process_default.nextTick(emitDrain, client);

next.js/packages/next/compiled/@edge-runtime/primitives/fetch.js

Line 5298 in 90ddd0d

define_process_default.nextTick(resume, this);

next.js/packages/next/compiled/@edge-runtime/primitives/fetch.js

Line 4222 in 90ddd0d

define_process_default.nextTick(() => {

next.js/packages/next/compiled/@edge-runtime/primitives/fetch.js

Line 571 in 90ddd0d

define_process_default.nextTick((stream3, err2) => {

---

I also noticed that this problem only happens during local development. The problem does not seem to exist when the application is actually deployed.

[dferber90]

Duplicate of:

• Regression: fetch requests in middleware fail with a body #38963
• fetch POST not working due to missing internals edge-runtime#61

[ghost]

is there a solution yet?

[dferber90]

See #38963 (comment)

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.