nextjs - ✅(Solved) Fix Next.js 16.2 build failed: Failed to fetch Google Fonts [2 pull requests, 8 comments, 5 participants]

nextjs2026-03-19 13:57:30

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

vercel/next.js#91653•Fetched 2026-04-08 01:02:47

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Timeline (top)

commented ×8cross-referenced ×1issue_type_added ×1subscribed ×1

Error Message

Error while requesting resource Error while requesting resource

Build error occurred Error: Turbopack build failed with 2 errors: next/font: error: next/font: error:

PR fix notes

PR #92713: chore: Bump reqwest to 0.13.2 (Fixes Google Fonts with Turbopack for Windows on ARM64)

Repository: vercel/next.js
Author: Badbird5907
State: closed | merged: True
Link: https://github.com/vercel/next.js/pull/92713

Description (problem / solution / changelog)

Fixes #91653

Running next dev with the latest Turbopack fails to fetch fonts on Windows ARM machines, resulting in an http2 feature is not enabled error. This issue was fixed in reqwest v0.13.2: https://github.com/seanmonstar/reqwest/pull/2927

Changed files

Cargo.lock (modified, +2/-2)
Cargo.toml (modified, +1/-1)

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.3.0: Wed Jan 28 20:56:42 PST 2026; root:xnu-12377.91.3~2/RELEASE_ARM64_T8142
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: N/A
  pnpm: 10.32.1
Relevant Packages:
  next: 16.2.1-canary.1 // Latest available version is detected (16.2.1-canary.1).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/pawelhoros/next-16.2-google-fonts

To Reproduce

Pull this repo, then npm run build.

`npm run build

build next build

▲ Next.js 16.2.1-canary.1 (Turbopack)

Creating an optimized production build ... Turbopack build encountered 2 warnings: [next]/internal/font/google/geist_e193ce59.module.css Error while requesting resource There was an issue establishing a connection while requesting https://fonts.googleapis.com/css2?family=Geist:[email protected]&display=swap

Import trace: Server Component: [next]/internal/font/google/geist_e193ce59.module.css [next]/internal/font/google/geist_e193ce59.js ./app/layout.tsx

[next]/internal/font/google/geist_mono_b4d4e0d7.module.css Error while requesting resource There was an issue establishing a connection while requesting https://fonts.googleapis.com/css2?family=Geist+Mono:[email protected]&display=swap

Import trace: Server Component: [next]/internal/font/google/geist_mono_b4d4e0d7.module.css [next]/internal/font/google/geist_mono_b4d4e0d7.js ./app/layout.tsx

Build error occurred Error: Turbopack build failed with 2 errors: [next]/internal/font/google/geist_e193ce59.module.css next/font: error: Failed to fetch Geist from Google Fonts.

Import trace: Server Component: [next]/internal/font/google/geist_e193ce59.module.css [next]/internal/font/google/geist_e193ce59.js ./app/layout.tsx

[next]/internal/font/google/geist_mono_b4d4e0d7.module.css next/font: error: Failed to fetch Geist Mono from Google Fonts.

Import trace: Server Component: [next]/internal/font/google/geist_mono_b4d4e0d7.module.css [next]/internal/font/google/geist_mono_b4d4e0d7.js ./app/layout.tsx

at ignore-listed frames`

Switching back to 16.1.7 and everything works.

Current vs. Expected behavior

Should build with success.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.3.0: Wed Jan 28 20:56:42 PST 2026; root:xnu-12377.91.3~2/RELEASE_ARM64_T8142
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: N/A
  pnpm: 10.32.1
Relevant Packages:
  next: 16.2.1-canary.1 // Latest available version is detected (16.2.1-canary.1).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Not sure

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

next build (local)

Additional context

No response

extent analysis

Fix Plan

The issue seems to be related to Next.js 16.2.1-canary.1 failing to fetch Google Fonts during the build process. To fix this, you can try the following steps:

Downgrade Next.js: Temporarily downgrade to Next.js 16.1.7, which is known to work.
Configure next/font: Make sure you have the next/font module configured correctly. You can do this by adding the following code to your next.config.js file:

module.exports = {
  //... other configurations ...
  experimental: {
    fontLoaders: [
      {
        loader: '@next/font/google',
        options: {
          // your google font options
        },
      },
    ],
  },
}

Check network connectivity: Ensure that your development environment has a stable internet connection to fetch Google Fonts.
Update next/font configuration: If you are using a custom next/font configuration, make sure it is compatible with Next.js 16.2.1-canary.1.

Verification

To verify that the fix worked, run npm run build again and check for any errors related to Google Fonts.

Extra Tips

Make sure to check the Next.js documentation for any updates on next/font configuration and compatibility.
If you are behind a proxy or have specific network settings, ensure that they are configured correctly to allow fetching Google Fonts.

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?

#api #ssr #installation #tensor shape #autograd error #cache error #pipeline error #runtime error #dependency conflict

Still need to ship something?

×6

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

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

nextjs - ✅(Solved) Fix Next.js 16.2 build failed: Failed to fetch Google Fonts [2 pull requests, 8 comments, 5 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

PR fix notes

PR #92713: chore: Bump reqwest to 0.13.2 (Fixes Google Fonts with Turbopack for Windows on ARM64)

Description (problem / solution / changelog)

Changed files

Code Example

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

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

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

Additional context

extent analysis

Fix Plan

Verification

Extra Tips

Still need to ship something?

TRENDING

nextjs - ✅(Solved) Fix Next.js 16.2 build failed: Failed to fetch Google Fonts [2 pull requests, 8 comments, 5 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

PR fix notes

PR #92713: chore: Bump reqwest to 0.13.2 (Fixes Google Fonts with Turbopack for Windows on ARM64)

Description (problem / solution / changelog)

Changed files

Code Example

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

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

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

Additional context

extent analysis

Fix Plan

Verification

Extra Tips

Still need to ship something?

RELATED_DISCOVERY

TRENDING