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 🙏🏼

[Gold240sx]

Worked for me 04/15/25

[hrbust-xuzhi]

Worked for me 05/18/25

[AjiNurAji]

thanks sayakiee

[ghost]

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

[shalomspage]

Restarting vs code worked for me.

[thiagocam-marleyspoon]

Thanks for the hint, I had a local proxy enabled and it worked after disabling it

[kanta1207]

Disconnecting the VPN made it work for me too. Thanks!

[hummxt]

Thanks dude.

[Gibson-Joseph]

Thanks @shalomspage

[yusupsupriyadi]

I'm experiencing the same issue, but I temporarily turned off the turbopack feature when running the application on the deployment side by removing --turbopack in package.json

[hczs]

thanks!! It worked for me!!!

[mathanprasannakumar]

Thanks , it worked. Can any one know why such issue is happening , any leads would be welcomed.

[Kamaruddheen]

Thanks man. It worked

[ozgeonline]

Installing the latest versions may not solve the problem. Following the next.js documentation seems to have solved the problem for now.
https://nextjs.org/docs/messages/built-in-next-font
npx @next/codemod built-in-next-font .
I install it and it worked for me

[quyettranvu]

I tried that command but still not resolved, it kept showing sporadically even my tries seem to be very strict.

[quyettranvu]

I'm experiencing the same issue, I really love the behind architecture how Turbopack built but I really got mad because of this building error. Does anyone have any other suggestions? Thanks in advance!

[quyettranvu]

I hope that the developer team of Turbopack will check this soon

[sridhar2193]

I just removed --turbopack in next dev scripts in package.json. Now it is working. But need to debug why it is failing with turbopack

[daribock]

This solved the problem for me too. 🚀

[qyl27]

Same issue, can be reproduced in next 15.2.0

[HenryOoO]

The same problem was solved by restarting the server

[stevenho0811]

delete node_modules folder, and reinstall, and delete .next folder solve my problem. and if you still facing same problem, try another network environment, and do it again.

[kybaloo]

It's the use of Turbopack, Adding this to next.config.js solved it for me:

const nextConfig = {
  experimental: {
    turbopack: false, // Désactive Turbopack
  },
};

module.exports = nextConfig;

[ukalpa]

Yeah, it seems to be related to Turbo, and the Google font Inter is used in the sample Turbo code.

If you don't want to remove --turbo, you can simply search for import { Inter } from "next/font/google"; in your repository and delete the related code. That should resolve the issue.

https://github.com/vercel/turborepo/blob/main/examples/with-tailwind/apps/web/app/layout.tsx

[cp3hnu]

Same issue, can be reproduced in next 15.2.3

[georgewwindsor]

bump, still a problem on latest

[ipcloudlive]

npx @next/codemod built-in-next-font .

This fixed the error

[GowthamTG]

This is still a issue in next 15.3.0

[damianpetroff]

I have a hinge that, at least in my case, it could be related to company VPN.
Anyone in the same case that could resolve the issue by disabling / working around the VPN/Firewall ?

[damianpetroff]

At least in my case, and I have the same log as OP, it really looks like a network issue while trying to fetch https://fonts.gstatic.com/*

[thhomas]

Yes same here, I have a corporate network using Zscaler and I had to switch to a free one to make it work.
It could be because turbopack is a Rust app and fails to use my specific Root CA Certificate but I could not find a way go through it.

[Hexi1997]

same

[aaronguostudio]

Same here, got the same issue with Zscaler

[josuefuentesdev]

In my case, using the Cloudflare VPN solved my issue. It might be related to network censorship in Spain.

[aixegorri]

Using Cloudflare Warp solves the problem. I can't say for sure that the reason is censorship in Spain due to LALIGA.