Laravel Bunny Fonts Laravel Package

Product Decisions This Supports

• Compliance/privacy feature work: Adopting this package is the concrete implementation step for a "remove Google Fonts third-party requests" decision. It lets you keep CDN-grade font delivery while eliminating the Google Fonts call that drives most GDPR complaints and DPA questions from EU customers.
• Framework upgrade planning: v2.1.1 explicitly declares Laravel 13 support. That converts "can we upgrade the app to Laravel 13?" from a blocked item into an unblocked one — worth checking against your dependency matrix before the next upgrade window is scheduled.
• Build vs. buy (build vs. adopt): The capability itself is small — a config file plus a Blade directive/component emitting @font-face/<link> tags. The decision is not "can we build this in an afternoon" (we can) but "do we want to own font-CDN markup, preconnect hints, and fallback handling forever." Default to adopt for standard sites; build only if font loading is a differentiated part of the experience.
• Use cases: marketing/content sites with EU traffic, multi-brand properties needing per-brand font sets, any product where legal has flagged third-party font requests, and teams that want CDN performance without operating a font pipeline.
• Roadmap signal: a maintained 2.x line with an active Dependabot cadence (this release bumps dependabot/fetch-metadata) is a minor but real supply-chain hygiene indicator — it argues against treating the package as abandoned.

When to Consider This Package

Consider it when:

• You are on a supported Laravel version (now including 13) and want a config-driven, low-ceremony way to serve fonts.
• Legal/security has flagged Google Fonts, and self-hosting a full font pipeline is disproportionate to the risk.
• You want a small, single-purpose dependency rather than pulling in an asset/design-system framework.
• You need per-environment or per-brand font configuration without touching templates.

Look elsewhere when:

• The requirement is genuinely "zero third-party requests" (strict DPA, public-sector, some enterprise security reviews). Bunny is a privacy-friendlier CDN, not a self-hosted one — you still need a self-hosting/Vite-based approach.
• You need advanced typography control: subsetting, variable-font axes, size-adjust/fallback metric matching, or preload orchestration tied to critical CSS. Do this in your asset pipeline.
• Fonts are a design-system concern already owned by a token/theming layer — a second source of truth creates drift.
• You are not on Laravel, or you are pinned to an older major that this release does not cover.

Release-specific read: v2.1.1 is a compatibility and maintenance release only — Laravel 13 support plus a CI action bump. There are no new features, no API changes, no deprecations, and no migration work. Adopting it is a constraint update, not a re-architecture.

How to Pitch It (Stakeholders)

To executives: This is a small, free, open-source dependency that closes a recurring legal question — whether our sites leak visitor IPs to Google via fonts. It replaces that with a privacy-oriented CDN, keeps page performance roughly where it is, and costs nothing in licensing. The new release simply confirms the package tracks current Laravel versions, so it is not a dead end we will have to rip out. Decision required: approve adoption as the standard font-delivery path, or fund self-hosting if Legal requires zero third-party requests.

To engineering: One config file plus a Blade-level include; no build-step changes, no runtime services, no data model. The v2.1.1 bump is a version-constraint change — expect a trivial PR. Cost is a small, single-maintainer dependency, so we should pin it and let Dependabot watch it, and be prepared to vendor or replace it if maintenance lapses (the surface area is small enough that an exit is cheap).

Ask: approve adoption for the upcoming release train, confirm with Legal whether CDN-hosted fonts satisfy our position or whether self-hosting is mandatory, and add the package to the dependency-review list ahead of the Laravel 13 upgrade.