- What does gubler/elixir-bundle do?
- gubler/elixir-bundle is a Symfony bundle that integrates Laravel Elixir asset versioning into Symfony templates. It reads Elixir's rev-manifest.json and exposes Twig helpers that resolve hashed CSS and JavaScript paths. That lets Symfony templates reference compiled assets without hardcoding cache-busted filenames. It is a legacy build-time integration, not a runtime asset server.
- Is gubler/elixir-bundle compatible with Symfony 6/7 and PHP 8?
- No current compatibility is documented, and the package was last released in January 2017 for the Symfony 2/3 era. Its Composer constraints, service definitions, and code are likely to fail on PHP 8.x and Symfony 6/7 without forking and dependency surgery. Before any spike, inspect composer.json and test in a pinned container rather than on a developer machine.
- How do I install gubler/elixir-bundle?
- Historically, installation meant requiring gubler/elixir-bundle with Composer and registering the bundle in a legacy Symfony application. Because the package is archived and has no current releases, any install attempt is a fork-and-vendor exercise, not a normal supported setup. Pin PHP, Symfony, Node, npm, and lockfiles if you must evaluate it in a legacy context.
- How does gubler/elixir-bundle resolve Laravel Elixir asset paths in Twig?
- The bundle reads the rev-manifest.json file produced by Laravel Elixir and uses it to map logical asset names to hashed filenames. Twig helpers then return the cache-busted paths for CSS and JavaScript, so templates do not embed hashes directly. This depends on the manifest existing at the expected path and being refreshed by the external Elixir/Gulp build.
- Does gubler/elixir-bundle run Laravel Elixir or Gulp builds?
- No. The bundle only consumes Elixir's manifest and provides Twig helpers; it does not run Gulp, Elixir, Node, or npm builds. You must supply the legacy Node/Gulp toolchain separately, including the gulpfile.js and Elixir dependencies. That separation means build failures can occur silently outside Symfony's Composer or container setup.
- Is gubler/elixir-bundle maintained or archived?
- gubler/elixir-bundle is archived, with its last release in January 2017, 3 stars, and 0 dependents. There are no upstream security patches, Symfony compatibility updates, CI signal, or meaningful community support. Adopting it shifts all maintenance, vulnerability remediation, and upgrade work to your team.
- Can I use gubler/elixir-bundle in a new Symfony project?
- No. It is not suitable for greenfield or modern Symfony applications because maintained options such as Webpack Encore, AssetMapper, and Vite cover asset compilation and versioning with active support. The bundle only makes sense as a short-lived compatibility layer inside an existing legacy Symfony application already standardized on Laravel Elixir.
- What are alternatives to gubler/elixir-bundle for Symfony asset versioning?
- Use Symfony Webpack Encore for Webpack-based teams, Symfony AssetMapper for low-tooling applications, or Vite for modern frontend workflows. These are maintained paths that handle asset compilation, hashed filenames, manifest resolution, and Twig integration without a legacy Gulp stack. Choose based on your existing frontend tooling and Symfony version rather than trying to preserve Elixir.
- How do I migrate from Laravel Elixir to Webpack Encore, AssetMapper, or Vite?
- Inventory every elixir() call, gulpfile.js, Twig helper usage, asset path, and deployment artifact first. Freeze the legacy build and document its outputs, then build a parallel Encore, AssetMapper, or Vite pipeline and compare artifacts. Cut over Twig templates and deployment scripts, and only then remove the bundle, Gulp dependencies, and legacy Node toolchain.
- What production risks should I consider with gubler/elixir-bundle?
- The main risks are abandonment, outdated npm transitive dependencies, Gulp 3-era incompatibilities on modern Node, silent asset build failures, and supply-chain exposure. There is no upstream support or security patching, and CI must own reproducible legacy Node builds. Treat adoption as a remediation bridge with a named owner, security review, and a firm exit plan.