Weave Code
Font Manager Laravel Package
neuralglitch/font-manager
Font Manager for Laravel simplifies self-hosting typography: browse and install Google Fonts, register local font families, generate CSS and @font-face rules, and serve optimized font assets without external requests.
Universal font manager for Symfony supporting multiple providers
Frequently asked questions about Font Manager
- How do I install neuralglitch/font-manager in a Laravel application?
- Install it with Composer using composer require neuralglitch/font-manager, then publish the package configuration so the font and export sections are available in your app. After publishing, review the build and export settings before running any commands. Because the package is pre-1.0, pin the installed version in composer.json.
- Can I self-host Google Fonts with this package instead of loading them from Google's CDN?
- Yes. The package lets you browse and install Google Fonts into your Laravel application and generate the CSS and @font-face rules needed to serve the files locally. That removes the external request to Google's CDN, which helps with privacy, performance, and offline or air-gapped environments.
- How do I register local font files as a font family?
- Register local font families through the package configuration, pointing each family at its font files. Once registered, the manager can generate the matching @font-face rules and include the family in CSS, SCSS, or other exports. Keep the file paths stable so regenerated artifacts stay consistent across environments.
- What export formats does the package generate?
- The 0.2 export system can generate CSS custom properties, SCSS variables and mixins, ESM JavaScript, a Tailwind config module, TypeScript definitions, and design-token artifacts in W3C, Figma Tokens Studio, and Style Dictionary formats. You enable only the formats your frontend actually consumes. Run fonts:formats and fonts:format:info to discover what is available and what each format produces.
- How do I disable automatic exports when running fonts:lock in CI?
- Pass the --no-export flag to fonts:lock to preserve the earlier behavior of locking fonts without writing export files. This is the recommended first step when adopting 0.2 in an existing pipeline. Once you have validated the generated output, you can enable exports deliberately or add them as a separate CI step.
- Does the package work with Vite, Webpack, and Laravel's AssetMapper?
- The package auto-detects the build tool and targets Vite by default, with support for Webpack and Laravel's AssetMapper. If detection is uncertain, such as in a mixed or customized setup, set build.tool explicitly in the configuration. Explicit configuration is safer for production pipelines than relying on auto-detection.
- How do I generate a Tailwind config or SCSS variables from my fonts?
- Configure the export section for the format you want, then run fonts:export or let fonts:lock generate it after locking. The Tailwind export produces a config module you can merge into your Tailwind setup, while the SCSS export provides variables and mixins for Bootstrap SCSS or custom stylesheets. Verify the generated paths match where your build expects to find them.
- Can I export design tokens for Figma Tokens Studio or Style Dictionary?
- Yes, design-token exports are supported for W3C format, Figma Tokens Studio, and Style Dictionary. This lets the same font source of truth feed design tooling as well as the frontend build. Enable only the token formats your tooling reads so you do not create unnecessary files.
- Are the generated font exports deterministic and safe to commit to version control?
- Exports are intended to be reproducible, but determinism and idempotency are the biggest risk areas for a pre-1.0 package, especially for Tailwind config modules, TypeScript definitions, and token files. Commit the generated files and watch for noisy diffs between runs and environments. If formatting churn appears, pin the package version and report the case upstream.
- Is neuralglitch/font-manager production-ready, and how do I upgrade from 0.1.x?
- Treat it as pre-1.0: API and configuration may change between minor releases, so pin the version and read release notes before upgrading. Configuration changes from 0.1.x are additive, but fonts:lock now auto-exports by default, which is a behavioral change for CI. Adopt incrementally by running fonts:lock --no-export first, then enabling one export format at a time.
Weaver
How can I help you explore Laravel packages today?