Module not found: Can't resolve '***\app\favicon.ico?__next_metadata__'

[Sir-Erwin]

Link to the code that reproduces this issue

https://github.com/Sir-Erwin/project-xenia.git

To Reproduce

1. npm run dev

(after compiling it starts to throw the following error)

Current vs. Expected behavior

I expected to see the code successfully seeing that I had made no modifications from what I got from npx create-next-app@latest.

However, it threw an error saying " Module not found: Can't resolve '***\project-xenia\app\favicon.ico?next_metadata' "

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 12085
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.11 // Latest available version is detected (14.2.11).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: N/A
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

create-next-app, Image (next/image), Metadata

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I even tested it out with the previous 14.x.x versions, and even a 13.5.x version but it's throwing the same error.

I tried removing favicon.ico, but it just throws more errors. And sometimes it doesn't even start compiling, or freezes when compiling. I need to kill the processes eventually.

When I tried reproducing this in sandbox tho, there didn't seem to be a problem.

My guess, it has something to do with Windows, like its paths and stuff...

[Sir-Erwin]

When I delete favicon.ico, I get the following error

Module not found: Can't resolve 'next/font/local/target.css?{"path":"app\layout.tsx","import":"","arguments":[{"src":"./fonts/GeistVF.woff","variable":"--font-geist-sans","weight":"100 900"}],"variableName":"geistSans"}

[samcx]

@Sir-Erwin Can you try the latest canary to see if you're experiencing with that as well?

Will have to install the release candidate of react and react-dom as well.

[Sir-Erwin]

Same response

[samcx]

@Sir-Erwin Just to confirm, this is with the as well? I'm surprised it's taking 15.5s to compile .

Also, which package manager are you using (since next info is showing N/A is showing empty for all of them)?

[Sir-Erwin]

Wait, what's repro...

I don't know, I just used "npx create-next-app@latest"

I had downloaded node and react about 6 months ago, but they seem to be up to date...

[samcx]

@Sir-Erwin Can you share with us what was above your screenshot (your entire terminal process from starting the next dev Development server)?

[Sir-Erwin]