- Is jeroenvdheuve/assetic-cache-busting-worker-bundle compatible with Laravel?
- No. It is a Symfony bundle, not a Laravel package: it registers a DependencyInjection extension and compiler pass that injects Assetic\Factory\Worker\CacheBustingWorker into AsseticBundle's factory worker chain. Laravel has no bundle registration mechanism, no Assetic factory, and no asset-dump step for it to hook into. Its Composer constraints also target Symfony 2.8/3.x and PHP 5.5–7.0, which conflict with modern Laravel.
- What does this bundle actually do for cache busting?
- It adds content-based fingerprints to dumped Assetic asset filenames, for example file-<hash>.css, so browsers fetch updated CSS, JS, and images after deployments. It works by registering Assetic's CacheBustingWorker in the AsseticBundle factory chain. The worker only runs inside an Assetic asset dump pipeline.
- How do I install assetic-cache-busting-worker-bundle?
- You install it with Composer, but only inside a Symfony application that already uses AsseticBundle and assetic/factory. The package is archived and last released on 2016-03-09, so a normal composer require will usually fail on modern PHP and Symfony constraints. There is no Laravel installation path.
- What Symfony and PHP versions does this package support?
- It is a 2016-era bundle with constraints around Symfony 2.8/3.x and PHP 5.5–7.0. It will not resolve against Symfony 6/7 or PHP 8.2+ used by current Laravel releases. Validate with composer why-not before attempting an install.
- How is the cache-busting worker registered or configured?
- Registration is automatic through the bundle's DependencyInjection extension and a compiler pass that adds the worker to AsseticBundle's assetic.factory worker chain. You do not wire it manually in Laravel-style service providers. There is no runtime seam for Laravel to register it.
- Is this package maintained and safe for production?
- No. It is archived, last released in 2016, has 2 stars and 0 dependents, and has no security response process or issue triage. The transitive Assetic dependency is also legacy: Symfony moved away from Assetic to Webpack Encore and later AssetMapper/Vite. The realistic cost is an abandoned dependency blocking PHP upgrades.
- What should I use for cache busting in Laravel instead?
- Laravel 9+ ships Vite, which emits content-hashed filenames and writes public/build/manifest.json; the @vite Blade directive and Vite::asset() resolve through the manifest. Legacy Laravel Mix apps use mix.version() and the mix() helper. Both provide native cache busting without this package.
- Can I use this bundle alongside Laravel Vite or Mix?
- No, and you do not need to. Vite and Mix already produce content-hashed asset URLs via their manifests. This bundle only plugs into Assetic's asset dump pipeline, which Laravel does not use. Adding it would create dependency conflicts without adding functionality.
- How do I cache-bust non-bundled assets like uploads or generated PDFs in Laravel?
- Vite and Mix only cover assets in their build pipeline. For uploads, generated PDFs, or tenant-specific images, use a small helper that wraps md5_file() against a cached manifest or uses filemtime() as a cheap ?v= token. Confirm whether your CDN strips query strings; if it does, prefer hash-in-filename.
- How can I check whether this package will install in my project?
- Run composer why-not jeroenvdheuve/assetic-cache-busting-worker-bundle to see blocking constraints, then composer update --dry-run. Also run composer why assetic/factory to confirm whether AsseticBundle is still present. For Laravel targets the check will normally fail, confirming the package is not viable.