nextjs - 💡(How to fix) Fix next/font/google fails to build on 16.2.3 — Turbopack font resolution broken [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#92669Fetched 2026-04-12 13:23:18
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Fix Action

Fix / Workaround

  1. Create any Next.js App Router project using next/font/google in app/layout.tsx
  2. Use fonts like Ubuntu and Rubik with weight arrays and CSS variables
  3. Build successfully on Next.js 16.1.7
  4. Upgrade to Next.js 16.2.3 (npm install [email protected])
  5. Run npm run build
  6. Build fails with font resolution errors

This also reproduced on 16.2.2. I am upgrading specifically to patch CVE-2026-23869 (CVSS 7.5, DoS via Server Components). There is no 16.1.x backport — 16.2.3 is the only available fix for the 16.x line. This means projects using next/font/google cannot patch a HIGH severity CVE without breaking their build.

Code Example

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11
Binaries:
  Node: 22.20.0
  npm: 10.9.3
Next.js: 16.2.3 (fails), 16.1.7 (works)
Deployment: Vercel Pro
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/vercel/next.js/issues

To Reproduce

  1. Create any Next.js App Router project using next/font/google in app/layout.tsx
  2. Use fonts like Ubuntu and Rubik with weight arrays and CSS variables
  3. Build successfully on Next.js 16.1.7
  4. Upgrade to Next.js 16.2.3 (npm install [email protected])
  5. Run npm run build
  6. Build fails with font resolution errors

Font configuration in layout.tsx:

import { Ubuntu, Rubik } from 'next/font/google'

const ubuntu = Ubuntu({ weight: ['300', '400', '500', '700'], subsets: ['latin'], variable: '--font-ubuntu', display: 'swap', })

const rubik = Rubik({ weight: ['300', '400', '500', '700'], subsets: ['latin'], variable: '--font-rubik', display: 'swap', })

Current vs. Expected behavior

Expected: Build succeeds, as it does on 16.1.7.

Actual: Build fails with multiple errors:

  • Failed to fetch 'Rubik' from Google Fonts
  • Can't resolve '@vercel/turbopack-next/internal/font/google/cssmodule.module.css'
  • http2 feature is not enabled during font/CSS resolution

This also reproduced on 16.2.2. I am upgrading specifically to patch CVE-2026-23869 (CVSS 7.5, DoS via Server Components). There is no 16.1.x backport — 16.2.3 is the only available fix for the 16.x line. This means projects using next/font/google cannot patch a HIGH severity CVE without breaking their build.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11
Binaries:
  Node: 22.20.0
  npm: 10.9.3
Next.js: 16.2.3 (fails), 16.1.7 (works)
Deployment: Vercel Pro

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

Font (next/font)

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

next build (local)

Additional context

Deployed on Vercel Pro. Issue reproduces locally on Windows 11. Not browser-specific — build fails before the app can start. Same regression was present in 16.2.2. The 16.2.3 changelog mentions Turbopack fixes but the font resolution issue persists.

extent analysis

TL;DR

Downgrade to Next.js 16.1.7 or wait for a patch release that addresses the font resolution issue in Next.js 16.2.3.

Guidance

  • Verify that the issue is specific to the next/font/google module by trying to build the project without it.
  • Check the Next.js changelog and GitHub issues for any known problems with font resolution in version 16.2.3.
  • Consider opening an issue on the Next.js GitHub repository to report the regression and request a fix.
  • If possible, test the project with a different version of Node.js or npm to rule out any environment-specific issues.

Example

No code snippet is provided as the issue is related to a specific version of Next.js and its interaction with the next/font/google module.

Notes

The issue seems to be a regression introduced in Next.js 16.2.2 and 16.2.3, which affects the next/font/google module. The fact that it works in 16.1.7 suggests that the problem is version-specific.

Recommendation

Apply workaround: Downgrade to Next.js 16.1.7 until a patch release is available that fixes the font resolution issue in 16.2.3, as downgrading is the only known way to resolve the issue without breaking the build.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING