Weave Code
Asset Minifier for Symfony Asset Mapper - Made by SensioLabs
Frequently asked questions about Minify Bundle
- Can I use sensiolabs/minify-bundle directly in Laravel 10+ without Symfony?
- Yes, but indirectly. The bundle targets Symfony 8’s AssetMapper (now UrnResolver), so you’ll need a custom Laravel service provider to bridge it with Laravel’s `asset()` helper. Start by wrapping the UrnResolver in a Laravel service and aliasing it in `config/app.php`. Avoid SensioFrameworkExtraBundle—use Symfony UX components instead.
- How do I handle Symfony 8’s HttpCache in Laravel’s caching layer?
- Bind Symfony’s HttpCache to Laravel’s Cache facade using a custom adapter (e.g., `stitcherhq/easy-cache`). Clear cache tags manually when assets update, or use Laravel’s `cache:tags` system. Test with `php artisan cache:clear` after minification to ensure consistency.
- Will this bundle work with Laravel Mix or Vite for dynamic assets?
- No, it’s designed for static assets (CSS/JS) and won’t integrate with Laravel Mix or Vite. Use minify-bundle only for Blade templates or hybrid apps where static files need minification. For SPAs, stick with Vite’s built-in optimization.
- What Laravel versions officially support sensiolabs/minify-bundle v1.2.0?
- Laravel 10+ is the best fit due to PHP 8.1+ alignment with Symfony 8’s strict typing. Laravel 9 may work with PHP 8.1 and manual type adjustments, but Symfony 7.x compatibility is dropped. Check your `composer.json` for `^8.0` constraints on Symfony packages.
- How do I configure minify-bundle for Blade templates if Symfony uses Twig?
- Blade and Twig syntax differ, so rewrite asset tags manually. Replace `{{ asset('file.css') }}` with raw PHP: `<?php echo app('asset.urn_resolver')->resolve('file.css'); ?>`. For dynamic paths, create a Blade directive extending Laravel’s `asset()` helper to proxy through UrnResolver.
- Are there conflicts with other Laravel asset packages like laravel-mix or vite-laravel?
- No direct conflicts, but avoid mixing pipelines. Use minify-bundle for static assets (e.g., legacy CSS/JS) and Laravel Mix/Vite for dynamic bundles. If you need both, configure them in separate `webpack.mix.js` or Vite entry points and merge outputs in `public/`.
- How do I test minify-bundle in a Laravel CI pipeline?
- Test with PHP 8.1+ and Symfony 8 components. Use `composer test` if the package includes tests, or manually verify minification with `php artisan asset:minify`. Check cache behavior by simulating asset updates and validating `cache:tags` in your tests.
- What’s the performance impact of Symfony 8’s UrnResolver in Laravel?
- Minimal if configured correctly. UrnResolver adds a slight overhead for path resolution, but caching via Symfony’s HttpCache or Laravel’s Cache facade mitigates this. Benchmark with `php artisan optimize` and compare against Laravel’s native asset handling.
- Can I use this bundle in production without additional caching layers?
- Not recommended. Symfony 8’s HttpCache or Laravel’s Cache facade is required for optimal performance. Without caching, repeated minification requests will slow down asset delivery. Use `stitcherhq/easy-cache` for cross-framework compatibility.
- Are there alternatives to sensiolabs/minify-bundle for Laravel asset minification?
- Yes. For modern Laravel (10+), prefer `laravel-mix` (Webpack) or `vite-laravel` for dynamic assets. For static files, consider `barryvdh/laravel-mix` with `laravel-mix-purgecss` or `filp/whoops` for debugging. If you need Symfony interop, `symfony/webpack-encore` bridges Symfony and Laravel asset pipelines.
Weaver
How can I help you explore Laravel packages today?