Repository navigation
fix(fonts): self-host DM Sans and DM Mono instead of Google Fonts - #98
lorenzocorallo wants to merge 4 commits into
Conversation
Loading the fonts from fonts.googleapis.com sent every visitor's IP address to Google, which the privacy policy then had to list as a recipient. The same faces now come from @fontsource packages and are bundled into the build: DM Mono 400/500 and DM Sans with the wght and opsz axes, with font-display: swap.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 51 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe project now loads DM Sans and DM Mono from local packages. Theme aliases and toast text use the DM Sans variable font family. ChangesLocal Font Setup
Priority: ⬇️ Low Change: Bug fix Merge Risk: ⚪ Minimal · up to
|
The dashboard loaded DM Sans and DM Mono from Google Fonts, so every visitor's IP address reached Google and the privacy policy had to list Google as a recipient. The fonts are now bundled from
@fontsource/dm-mono(400, 500) and@fontsource-variable/dm-sans(opsz.css: wght and opsz axes, latin and latin-ext,font-display: swap), served from/assets. The Fontsource family is calledDM Sans Variable, so the--font-*tokens and the toast style point to it; the rendered faces are the same.Verified:
pnpm check,typecheck,testandbuildpass. The build output has nogoogleapis/gstaticreferences and emits the six woff2 files (DM Mono 400/500 and DM Sans opsz, latin and latin-ext each).