Verify canary release

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

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home Single Language
    Binaries:
      Node: 18.16.0
      npm: N/A
      Yarn: N/A
      pnpm: 8.4.0
    Relevant packages:
      next: 13.4.6-canary.7
      eslint-config-next: 13.4.5
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3

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://github.com/4nur4g/nextapppnpm

To Reproduce

Just run the development server by, I'm running it using: pnpm run dev, the issue remains even if I use the --turbo flag.

For reproducing from scratch:

• pnpm create next-app

√ What is your project named? ... nextapppnpm
√ Would you like to use TypeScript with this project? ... No / Yes
√ Would you like to use ESLint with this project? ... No / Yes
√ Would you like to use Tailwind CSS with this project? ... No / Yes
√ Would you like to use src/ directory with this project? ... No / Yes
√ Use App Router (recommended)? ... No / Yes
√ Would you like to customize the default import alias? ... No / Yes

Keep on entering for every prompt, i.e. default values.

• pnpm install
• pnpm run dev

Check the log window. You'll find the warning.

Describe the Bug

When I start the development server, it logs the warning, even when I don't change the app created by create next app.

Expected Behavior

There should be no such warning, especially when the app wasn't touched after it was created using create next app.

Which browser are you using? (if relevant)

Microsoft Edge

How are you deploying your application? (if relevant)

No response