Next.js v12.0.8 - Nx executor seem to run Next in a custom server

Current Behavior

Seems like Next.js identifies the server nx’s executor is using as a custom server.

More details on my original ticket in next’s repo - https://github.com/vercel/next.js/issues/33450

Expected Behavior

Should use Next’s server as is.

Steps to Reproduce

• Create a repo with Next.js app
• Update Next.js to v12.0.8
• Add middleware as described here - https://github.com/vercel/next.js/issues/33450

This issue may not be prioritized if details are not provided to help us reproduce the issue.

Failure Logs

 Error: To use middleware you must provide a `hostname` and `port` to the Next.js Server

Environment

  Node : 16.13.0
  OS   : darwin x64
  yarn : 3.1.0
  
  nx : 13.4.6
  @nrwl/angular : undefined
  @nrwl/cli : 13.4.6
  @nrwl/cypress : 13.4.6
  @nrwl/devkit : 13.4.6
  @nrwl/eslint-plugin-nx : 13.4.6
  @nrwl/express : undefined
  @nrwl/jest : 13.4.6
  @nrwl/linter : 13.4.6
  @nrwl/nest : undefined
  @nrwl/next : 13.4.5
  @nrwl/node : 13.4.6
  @nrwl/nx-cloud : undefined
  @nrwl/react : 13.4.6
  @nrwl/react-native : undefined
  @nrwl/schematics : undefined
  @nrwl/tao : 13.4.6
  @nrwl/web : 13.4.6
  @nrwl/workspace : 13.4.6
  @nrwl/storybook : 13.4.6
  @nrwl/gatsby : undefined
  typescript : 4.5.4
  rxjs : 6.6.7
  ---------------------------------------
  Community plugins:
         nx-stylelint: 13.1.0

[jfabraxas]

I had the same issue. As a workaround you can add the port and hostname to workspace.json, worked for me

{
   "app": {
      "serve": {
         "builder": "@nrwl/next:server",
         "options": {
            "port": 4200,
            "hostname": "localhost"
         }
      }
   }
}

[babie]

FYI:

DOS Vulnerability for self-hosted next.js apps using i18n https://github.com/vercel/next.js/security/advisories/GHSA-wr66-vrwm-5g5x