An error occurred in next/font.

[Ajay01103]

Link to the code that reproduces this issue

https://github.com/Ajay01103/Next-14.2.0

To Reproduce

1). start the the local development server
2). An error occurred in next/font.

Current vs. Expected behavior

I was trying the latest version of next js 14.2.0 after the installation finished and run the local development server the error appear which is like

An error occurred in next/font.
inside src\app\layout.tsx

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home Single Language
  Available memory (MB): 15732
  Available CPU cores: 12
Binaries:
  Node: 20.12.1
  npm: N/A
  Yarn: N/A
  pnpm: 8.15.6
Relevant Packages:
  next: 14.2.0 // Latest available version is detected (14.2.0).
  eslint-config-next: 14.2.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A

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

App Router, CLI (create-next-app)

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

next dev (local), next build (local), next start (local), Vercel (Deployed)

Additional context

I tested the next js 14.1.4 it just worked fine bu the latest version of next js 14.2.0 is throwing the error inside src\app\layout.tsx

[AtharvaChobe]

Yes, I am also getting that same error

[ghimireaacs]

Getting same error, what a day to start learning NextJS. 😂

[byronlove111]

i'm getting it too lmaooo, waiting for a fix

[ElironB]

Also getting it

[Thanaen]

Duplicate of #64371

[byronlove111]

Duplicate of #64371

thanks ! it worked

[timneutkens]

Closing as duplicate of #64371

[wagstalos]

https://nextjs.org/docs/messages/built-in-next-font

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.