- Can I use kachkaev/assets-version-bundle in a Laravel application?
- No. It is a Symfony 2/3 bundle with no Laravel service provider or package-discovery metadata, so Composer will install it but Laravel will not register its services, Twig helpers, or console command. The mechanics rely on Symfony's AppKernel, DI parameters, and Twig, none of which exist in a standard Laravel app. Use Laravel's native Vite or Mix cache busting instead.
- How do I install kachkaev/assets-version-bundle?
- In a legacy Symfony 2/3 project, install it with composer require kachkaev/assets-version-bundle and register the bundle in AppKernel. Configuration goes under the kachkaev_assets_version YAML namespace. There is no Laravel installation path because Laravel does not use Symfony bundles or AppKernel registration.
- What Laravel versions does kachkaev/assets-version-bundle support?
- None. The package targets Symfony 2.x and 3.x, whose 2.8 and 3.4 releases reached end of life in 2018 and 2021 respectively. Its PHP version constraints will also fail to resolve against modern PHP 8.2/8.3 base images without --ignore-platform-reqs. It is not a Laravel package and has no Laravel version compatibility.
- How does kachkaev/assets-version-bundle do cache busting?
- It appends a configurable version identifier, usually as a query string, to asset URLs generated through its Twig integration. The version can come from a static value, Git metadata, or a custom service, and a Symfony console command can rewrite the version parameter in place. This gives a single global version string rather than per-file content hashes.
- Does kachkaev/assets-version-bundle support per-file cache busting?
- No. It uses one global version string for all assets, so every deployment changes every asset URL and forces browsers to re-download unchanged CSS, JavaScript, and images. Laravel's Vite and Mix pipelines use content-hashed filenames and manifests, which give per-file granularity and keep unchanged assets cached. That makes the bundle's model strictly worse for modern front-end delivery.
- What should Laravel developers use instead of kachkaev/assets-version-bundle?
- Use Laravel Vite with @vite, Vite::asset(), and the generated manifest for per-file cache busting on Laravel 9 and later. For legacy Mix projects, use mix() with mix-manifest.json. If you genuinely need a global version string, add a small Blade helper that reads config('app.assets_version') from a deploy-time environment variable.
- How do I configure kachkaev/assets-version-bundle?
- Configuration is YAML-based under the kachkaev_assets_version namespace in a Symfony app, where you choose a static version, Git-derived version, or custom service. There is no Laravel config file, no config() integration, and no environment-variable binding in the package. In Laravel you would have to rewrite this configuration layer entirely, which is not worth doing.
- Is kachkaev/assets-version-bundle maintained and safe for production?
- The upstream repository is archived, has roughly 57 stars and zero dependents, and targets Symfony versions that are long past end of life. There is no active community to absorb a fork and no security triage path. Its PHP constraints also conflict with modern PHP 8.2/8.3 images without platform-req overrides, which is a red flag for production use.
- How would I test asset versioning in Laravel?
- Use Laravel's built-in testing tools to assert that rendered pages reference the expected Vite or Mix manifest URLs, and verify that manifest filenames change when asset contents change. For deploy-level confidence, add a smoke test that fetches a page after deployment and checks that CSS and JavaScript URLs resolve. You cannot test kachkaev/assets-version-bundle in Laravel because its Twig helpers and Symfony console command are never registered.
- Does kachkaev/assets-version-bundle handle CDN cache invalidation?
- No. A query-string version bump changes the URL that browsers request but does not purge edge caches, so a CDN can still serve stale content unless you invalidate it or use hashed filenames. In Laravel deployments you should pair Vite's hashed assets with a post-deploy CDN invalidation step in CI, such as a CloudFront invalidation or your provider's equivalent.