Will It Vibe?Deprecated @next/font import
Part of Dependencies & Hygiene, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
The @next/font package was merged into the framework as next/font and the standalone package is deprecated. Staying on @next/font blocks upgrades and misses fixes shipped only to the built-in module.
Why it matters
The @next/font package was folded into the framework as next/font, and the standalone @next/font package is deprecated. Continuing to import from it means you miss fixes that ship only to the built-in module and it becomes a blocker when upgrading to a newer major version of Next.js.
How to fix it
Change the import source from @next/font to next/font. The subpaths are the same: @next/font/google becomes next/font/google and @next/font/local becomes next/font/local. Then remove @next/font from package.json since it is no longer needed.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo