- Is jeroenvdheuve/assetic-cache-busting-worker a Laravel package?
- It is not a Laravel package. It is a standalone PHP worker for projects using the Assetic asset pipeline, and it does not provide a Laravel service provider, configuration file, facade, or Blade helper. Using it in Laravel would require custom wiring around Assetic rather than normal Laravel asset resolution.
- How do I install jeroenvdheuve/assetic-cache-busting-worker with Composer?
- You would normally install it with Composer using the package name jeroenvdheuve/assetic-cache-busting-worker, but first check the composer.json constraints. The project was last released in 2015 and is archived, so it may conflict with PHP 8+, modern Symfony components, and current Laravel dependencies. Test only in an isolated legacy branch with pinned dependencies.
- Does this package support Laravel 10, Laravel 11, or Laravel 12?
- There is no evidence of support for modern Laravel versions. The package is not Laravel-native and assumes an Assetic pipeline, while supported Laravel versions use Vite or Mix manifests. For Laravel 10, 11, or 12, use laravel-vite-plugin or Laravel Mix instead of this worker.
- Is assetic-cache-busting-worker compatible with PHP 8?
- Compatibility with PHP 8 is unverified and likely problematic because the package was last released in 2015 and is archived. Its Composer constraints probably target older PHP and Symfony or Assetic versions. Confirm with Composer before any trial and expect to run it only on a matching legacy PHP runtime.
- How does this worker add cache busting to Assetic assets?
- It scans compiled assets and produces hash-suffixed filenames so browsers request new CSS and JavaScript after a deployment. The intent is to keep generated asset references consistent between templates and files. The exact worker contract is undocumented here, so verify whether it rewrites filenames, emits a manifest, or injects URLs at runtime.
- Can I use this package with Laravel Mix or Vite?
- No, it is built for the Assetic pipeline, not Laravel Mix or Vite. Mix and Vite use their own manifest-based asset resolution, and mixing Assetic with either in the same asset graph is risky. For Laravel, use laravel-vite-plugin or Mix rather than adding an Assetic worker.
- Is jeroenvdheuve/assetic-cache-busting-worker maintained and safe for production?
- It is effectively unmaintained: archived, last released in 2015, and with zero stars or dependents in the assessment. There are no upstream bug or security fixes, and support is unavailable. MIT licensing allows forking, but that does not reduce the operational risk of making it a long-lived production dependency.
- What are the best alternatives for cache busting in Laravel?
- For modern Laravel, use Vite through laravel-vite-plugin; Laravel Mix is an option for older applications. You can also implement a small content-hash build step if you need custom filenames. For Symfony, consider AssetMapper or Encore, and avoid mixing those pipelines with Assetic.
- How do I migrate from Assetic cache busting to Laravel Vite?
- Inventory the existing asset pipeline, manifest format, and cache headers first. Capture the expected hashed URLs from the legacy Assetic worker, implement an equivalent in Vite or a content-hash build step, and run side-by-side URL verification. Then cut over CDN and cache rules and remove Assetic and the worker.
- How should I test this worker before using it in a legacy deployment?
- Use an isolated legacy environment, such as a Docker image with the matching old PHP runtime and pinned dependencies. Add golden tests for generated asset URLs and manifests, and check determinism, CDN behavior, and opcache implications. Do not add it to a supported Laravel application's dependency graph.