- Is konstantin-kuklin/assetic-static-gzip-bundle a Laravel package?
- No. It is a Symfony bundle that hooks into AsseticBundle, which is registered through the Symfony kernel's bundle system. There is no Laravel service provider, no publishable config, and no Composer extra.laravel block. Laravel has no equivalent bundle contract for it to register against.
- Can I use AsseticStaticGzipBundle in a Laravel application?
- Not through any supported path. Loading it would mean re-implementing Symfony bundle bootstrapping inside Laravel, which no team should maintain in production. Even if it booted, it depends on assetic/assetic and assetic-bundle, which are abandoned and will likely conflict during Composer resolution against a modern Laravel foundation.
- How do I install assetic-static-gzip-bundle?
- On Symfony you require the package with Composer and register the bundle in AppKernel.php on Symfony 2 and 3, or in config/bundles.php on Symfony 4 and later. It also expects assetic-bundle to be installed and configured with a dump step. There is no Laravel installation procedure because the bundle is never loaded by the framework.
- Which PHP and Symfony versions does AsseticStaticGzipBundle support?
- The codebase was written for the PHP 5.x and Symfony 2.x era, when Assetic was still a core part of the Symfony asset pipeline. Assume it is incompatible with PHP 8.x and with any currently supported Symfony or Laravel release. If a compatibility check is required, timebox it to a single engineer day to confirm the Composer conflict and record that as the closure rationale.
- What does AsseticStaticGzipBundle actually do?
- It hooks into the Assetic dump process and writes a .gz sibling next to each compiled CSS and JavaScript file. A web server configured with gzip_static then serves those precompressed files directly to clients that send Accept-Encoding: gzip. The scope is narrow: it only emits the compressed artifacts, it does not handle caching, fingerprinting, or CDN behaviour.
- Is assetic-static-gzip-bundle still maintained?
- There is no meaningful maintenance signal. The repository has roughly 14 stars and zero dependents, a single maintainer, and no visible release cadence, so there is no production validation or community security review behind it. Its dependency tree is the abandoned assetic/assetic and assetic-bundle packages, which have no realistic upgrade path if a CVE lands.
- What is the best Laravel alternative to AsseticStaticGzipBundle for gzip compression?
- Use the build tooling you already have. With Laravel and Vite, add a compression plugin such as vite-plugin-compression so the build emits .gz and .br files alongside the hashed assets; with legacy Laravel Mix, add compression-webpack-plugin in webpack.mix.js. Then enable gzip_static on in nginx, or the Apache equivalent, to serve the precompressed files. This adds no runtime dependency and no framework coupling.
- Does AsseticStaticGzipBundle work with Vite or Laravel Mix?
- No. It only operates inside the Assetic dump pipeline, which is a Symfony concept removed from modern Symfony and absent from Laravel. Vite, Webpack, and Encore each have first-class compression plugins that produce the same .gz artifacts with far less risk. If you are already on Vite or Mix, this package has nothing to contribute.
- How do I serve precompressed .gz assets and verify they are used?
- Enable gzip_static on; in your nginx server or location block, or use the equivalent precompressed negotiation in Apache. Request a CSS or JS file with curl and an Accept-Encoding: gzip header, then confirm the response carries Content-Encoding: gzip and Vary: Accept-Encoding. Also check that your CDN is not double-compressing content that the origin already compressed.
- Should I add AsseticStaticGzipBundle as an interim step while migrating off Assetic?
- No. Adding it lengthens the life of a dependency you are trying to remove and introduces an unpatched transitive tree into your supply chain in the meantime. Instead, inventory the current Assetic dump outputs, stand up Vite or Encore to produce equivalent artifacts, enable gzip_static at origin behind a canary, verify the response headers, then decommission Assetic and this bundle together.