Unable to use the middleware feature with React 18 & output:standalone feature

Verify canary release

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

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #137-Ubuntu SMP Wed Jun 15 13:33:07 UTC 2022
Binaries:
  Node: 17.8.0
  npm: 8.5.5
  Yarn: 1.22.19
  pnpm: N/A
Relevant packages:
  next: 12.2.3
  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)

standalone / server.js / docker

Describe the Bug

It’s currently impossible to use the middleware feature with React18 and the output:standalone feature. Trying to force the experimental.runtime:nodejs has no effect.

The simplest middleware, like a more complicated, result to the same issue.

import { NextResponse } from 'next/server'

export const middleware = async (request) => {
  console.log(request)
}

Real example:

/* eslint-disable @next/next/no-server-import-in-page */
import type { NextRequest } from 'next/server'
import { NextResponse } from 'next/server'

import { COOKIE_JWT_HP } from '@/services/auth'
import { routes } from '@/utils/route'

export const middleware = async (request: NextRequest) => {
  if (request.nextUrl.pathname === '/') {
    if (!request.cookies.get(COOKIE_JWT_HP)) {
      return
    }

    const url = request.nextUrl.clone()
    url.pathname = routes.dashboard
    return NextResponse.redirect(url)
  }
}

export const config = {
  matcher: ['/'],
}

The error:

Error: Cannot find module 'next/dist/compiled/@edge-runtime/primitives/console'
Require stack:
- /app/node_modules/next/dist/compiled/edge-runtime/index.js
- /app/node_modules/next/dist/server/web/sandbox/context.js
- /app/node_modules/next/dist/server/web/sandbox/sandbox.js
- /app/node_modules/next/dist/server/web/sandbox/index.js
- /app/node_modules/next/dist/server/next-server.js
- /app/server.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.resolve (node:internal/modules/cjs/helpers:108:19)
    at addPrimitives (file:///app/node_modules/next/dist/compiled/edge-runtime/index.js:1:983)
    at Object.extend (file:///app/node_modules/next/dist/compiled/edge-runtime/index.js:1:388)
    at new VM (file:///app/node_modules/next/dist/compiled/edge-runtime/index.js:1:7886)
    at new EdgeVM (file:///app/node_modules/next/dist/compiled/edge-runtime/index.js:1:348)
    at new EdgeRuntime (file:///app/node_modules/next/dist/compiled/edge-runtime/index.js:1:8590)
    at createModuleContext (file:///app/node_modules/next/dist/server/web/sandbox/context.js:71:21)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.getModuleContext (file:///app/node_modules/next/dist/server/web/sandbox/context.js:41:25)

Expected Behavior

No error.

Link to reproduction

https://github.com/webda2l/nextjs-issue1

To Reproduce

Build the docker, and run it http://localhost:3000/

[ref-thomasledoux1]

It seems like the “next/dist/compiled/@edge-runtime” dependency is not being picked up correctly by the tracing feature used by the outputstandalone… We added the following to our catch-all route (pages/[[…slug]]):

export const config = {
  unstable_includeFiles: [
    'node_modules/next/dist/compiled/@edge-runtime/primitives/**/*.+(js|json)',
  ],
}

This seems to have done the trick for now.

[ref-thomasledoux1]

Good to hear! Hope this gets picked up by the team to fix it 😃