Next dev CLI does not tell config errors before automatically stopping

[busybox11]

Verify canary release

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

Provide environment information

❯ npx next info

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PREEMPT_DYNAMIC Fri, 11 Aug 2023 11:03:36 +0000
    Binaries:
      Node: 20.5.0
      npm: 9.8.1
      Yarn: 1.22.19
      pnpm: 8.5.1
    Relevant Packages:
      next: 13.4.20-canary.0
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/nifty-nova-46w2sz?file=%2Fnext.config.js%3A18%2C4

To Reproduce

First, run the dev server with next dev. Everything should work fine.

Then try to append an invalid async headers() function to your next.config.js, and let the dev server reload itself (see pic attached).

Mine was the following :

async headers() {
  return [
    {
      source: '/_next/static/media/*',
      headers: [
        {
          key: 'Cache-Control',
          value: 'public, max-age=31536000, immutable',
        },
      ],
    }
  ]
}

Describe the Bug

While reloading itself, the dev server doesn't tell about the config error and just crashes without logging anything, nor an error code (see green arrow on the beginning of the line following the last log - that means it exited with code 0).

nextjs_headers_dev_cli.mp4

Expected Behavior

The error should at least be mentionned, and perhaps the server should exit with a code other than 0.

(This behavior could also be used for the next next dev that will log the error before stopping, an error code would be a good thing here too).

Which browser are you using? (if relevant)

/

How are you deploying your application? (if relevant)

/

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!