# How to Fix "Module not found: Can't resolve 'next/font/google'" in v0 - Tool: Vercel v0 - Difficulty: Intermediate - Fix time: 10-20 minutes - Compatibility: Vercel v0 projects (Next.js 13+) - Last updated: March 2026 ## TL;DR The 'Module not found: Can't resolve next/font/google' error in Vercel v0 means the Next.js font module cannot be found during build. This happens when the Next.js version is incompatible, the project was exported from v0 without proper dependencies, or Turbopack has a resolution bug. Update Next.js to the latest version, ensure @next/font is not mixed with the built-in next/font, and check your package.json. ## What does "Module not found: Can't resolve 'next/font/google'" mean? This error appears during the Next.js build when the font module from next/font/google cannot be resolved. The next/font module is built into Next.js 13.2+ and provides automatic font optimization. Variants of this error include: Can't resolve '@vercel/turbopack-next/internal/font/google/font' (Turbopack-specific) and Can't resolve 'next/font/google/target.css'. In v0 projects, this error is common because v0 generates code that uses next/font/google for typography, but the module resolution can fail when the project is exported or deployed. The v0 sandbox may use a different Next.js version than what gets installed in your production deployment. The Turbopack variant (@vercel/turbopack-next) is specific to projects using the Turbopack bundler (the experimental default in newer Next.js versions) and indicates an internal resolution path issue rather than a missing package. ## Common causes - **The Next.js version installed is** — older than 13.2, which is when next/font was moved from @next/font to the built-in next/font module - **The project mixes @next/font (old** — separate package) and next/font (built-in) imports, causing resolution conflicts - **Turbopack has a font resolution bug that** — fails to resolve the internal Google Fonts module path - **The node_modules directory is corrupted or** — incomplete, missing the Next.js font module files - **V0 generated code references next/font/google** — but the exported project has a Next.js version that does not include it - **Package-lock.json or yarn.lock has stale entries that** — prevent proper Next.js module resolution ## How to fix "Module not found: Can't resolve 'next/font/google'" First, check your Next.js version in package.json. The next/font module requires Next.js 13.2 or later. If your version is older, update it: npm install next@latest. If you have both @next/font and next/font imports, consolidate to next/font (the built-in version). Remove the @next/font package: npm uninstall @next/font. Then update all imports from '@next/font/google' to 'next/font/google'. For Turbopack-specific errors: try switching to Webpack by removing the --turbo flag from your dev command in package.json. If you want to keep Turbopack, update Next.js to the latest canary version which may have the fix. Clean install as a fallback: delete node_modules, delete package-lock.json (or yarn.lock), and run npm install fresh. This resolves corrupted or stale module resolution. For v0 projects specifically: after exporting, ensure your package.json has next at version 14.0+ (or the latest stable). V0 projects are built on Next.js App Router, which requires a recent version for all features to work correctly. Before: ``` // Old @next/font import (deprecated) import { Inter } from '@next/font/google'; // Or Turbopack internal path import { Inter } from '@vercel/turbopack-next/internal/font/google/font'; ``` After: ``` // Correct built-in import (Next.js 13.2+) import { Inter } from 'next/font/google'; const inter = Inter({ subsets: ['latin'], display: 'swap', }); // In your layout.tsx export default function RootLayout({ children }) { return ( {children} ); } ``` ## Tips to prevent this - Use the built-in next/font/google import (not @next/font/google) and ensure Next.js is version 13.2 or later - After exporting from v0, run npm install next@latest to ensure font modules are available in the production build - If Turbopack has font resolution issues, switch to Webpack by removing --turbo from the dev script temporarily - Delete node_modules and lock files for a clean install when module resolution errors persist after version changes ## Frequently asked questions ### Why does my v0 project fail with "Module not found: Can't resolve 'next/font/google'"? V0 generates code using next/font/google for typography. This module is built into Next.js 13.2+. If your deployed version uses an older Next.js or has a corrupted node_modules, the import fails. Update Next.js and do a clean install. ### What is the difference between @next/font and next/font? @next/font was a separate package used before Next.js 13.2. Starting with 13.2, font optimization was moved into the core next package as next/font. The @next/font package is now deprecated. Use next/font/google for all new projects. ### Does Turbopack cause font resolution errors? Yes, some Turbopack versions have a bug resolving the internal font module path (@vercel/turbopack-next/internal/font/google/font). Switch to Webpack temporarily or update Next.js to the latest version which may include a fix. ### How do I do a clean install to fix module resolution? Delete node_modules and your lock file (package-lock.json or yarn.lock), then run npm install. This forces a fresh download of all dependencies and rebuilds the module resolution tree from scratch. ### Can RapidDev help fix v0 project build errors? Yes. RapidDev can resolve dependency version conflicts, fix module resolution issues, configure proper font loading, and set up a CI/CD pipeline that catches these errors before deployment. --- Source: https://www.rapidevelopers.com/ai-build-errors/module-not-found-cant-resolve-next-font-google © RapidDev — https://www.rapidevelopers.com/ai-build-errors/module-not-found-cant-resolve-next-font-google