AI & Agent Dev Bug Sandbox Back to Radar

Next/Font/Google Fails When Google Fonts Returns Extensionless /L/Font?Kit= URLs

Google Fonts occasionally returns extensionless URLs with a format('woff2') hint. Next.js font loaders assume a file extension in the URL, causing webpack to crash with a null regex match and Turbopack to split the URL query on '&', resulting in intermittent build failures.

highConfidence 93%Next.js Affected V16.2.12 Affected V16.3.6 Affected V16.4.0-Canary.40

Origin Analysis

Webpack uses a non-null assertion on a regex that requires a file extension at the end of the Google Fonts URL. Turbopack additionally parses JSON-serialized options through QString::from, which splits the URL's query string on '&', creating multiple query entries and causing a bailing check; the Rust loader also rejects URLs without an extension.

1. Clone https://github.com/jasonwbarnett/next-font-google-extensionless-url\n2. Run `npm install`\n3. Run `npm run build:webpack` and `npm run build:turbopack`\n4. The builds fail with the errors described in the issue. Control mocks using normal .woff2 URLs pass.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

The fallback to 'woff2' assumes Google serves woff2 for the Chrome User-Agent; if a different format is served without a hint, the font file may be misclassified. The percent-encoding change in Rust may affect older Turbopack versions that decode query values differently; test thoroughly with legacy project structures. Rollback: revert the patch and pin Next.js to a version before the change if regressions occur in custom font pipelines. Also ensure existing font file hashes remain unchanged to avoid cache invalidation cascades.