Can't resolve '@vercel/turbopack-next/internal/font/google/font' sporadically on next dev --turbo.

[lancejpollard]

Summary

Keep getting this sporadically when I start my server, then I have to try and try again to restart it, until it finally works.

Additional information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:51 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6030
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 8.10.0
Relevant Packages:
  next: 14.1.1-canary.46 // Latest available version is detected (14.1.1-canary.46).
  eslint-config-next: 13.1.5
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A

Example

No response

[Sayakie]

I faced same issue and resolved by installing latest version issued: pnpm add next@latest

[vrease]

Thanks Sayakie 🙏🏼

[luc345]

I am also experiencing the same issue with the error message: Module not found: Can't resolve '@vercel/turbopack-next/internal/font/google/font'. I have already updated all packages to the latest versions. Does anyone know how to resolve this? Thank you!

[shashicode]

I am still facing the same issue, tried reinstalling and adding the latest next, but nothing works, Has anyone found a fix yet?
these are building blocks of an application why this does not work :(

[niikkhilsharma]

Faced the same issue, I tried restarting the server and it worked for me.

[rsignavong]

I have the issue. How can I fix it?

[Nonellia]

Hey, did you solve it?

[devmev10]

Faced the same out of nowhere.
installing nextjs latest version and restarting vscode worked

npm install next@latest

[devmev10]

it stopped working again. and now even restarting doesn't work.
Guess, have to find a permanent fix

[devmev10]

Found the issue - VPN!

on disabling, it worked.

[fegig]

I think it mostly has to do with networks. In my case, I had to turn on VPN before the issue went away.

[shalomspage]

I am facing the same issues. Do you know how I can fix it?

[shalomspage]

Restarting vs code worked for me.