- Can I use sanpi/assetic-bundle in a Laravel application?
- No. This is a Symfony bundle that registers Assetic with the Symfony kernel and exposes Twig tags, so it depends on Symfony's bundle registration and configuration layers that Laravel does not have. Laravel's equivalents are Vite through laravel-vite-plugin, or the older Laravel Mix. Do not try to bridge it into a Laravel app.
- How do I install sanpi/assetic-bundle?
- Run composer require sanpi/assetic-bundle, register the bundle in AppKernel (Symfony 2/3) or config/bundles.php (Symfony 4), import the assetic configuration block, and make sure the filter binaries you use (lessc, sass, uglify-js) exist in your build image. Because the package has zero stars and zero dependents, pin it to a specific commit or tag via a Composer repositories entry rather than a floating constraint. Record the fork's provenance in an ADR.
- Which Symfony and PHP versions does sanpi/assetic-bundle support?
- The fork exists to keep the Assetic integration installable on a newer Symfony and PHP baseline than the abandoned upstream bundle, but the exact constraints must be read from its composer.json. Forks of this kind typically loosen symfony/* and PHP bounds to stay installable, which trades a clean install for untested runtime combinations. Check whether those declared ranges are actually exercised in CI before you rely on them.
- Is sanpi/assetic-bundle actively maintained?
- There is no meaningful maintenance signal: zero stars, zero dependents and a zero score indicate no observable adoption or community validation. The upstream symfony/assetic-bundle was deprecated and removed from the core distribution around Symfony 4 and has been effectively unmaintained since. Treat this fork as a frozen compatibility shim, not a living dependency.
- What is the difference between sanpi/assetic-bundle and symfony/assetic-bundle?
- It is a community fork of the deprecated upstream bundle, created to keep the same integration installable on newer Symfony and PHP versions. The exact delta is unknown unless you diff it against the last upstream release, and forks frequently carry unmerged local patches, relaxed constraints or abandoned experiments. Reviewing that diff, or forking upstream in-house, is the safer route.
- Does sanpi/assetic-bundle support the Twig javascripts and stylesheets tags?
- Yes, it registers the Assetic Twig tags such as {% javascripts %} and {% stylesheets %}, along with the assetic: configuration blocks the templates expect. The catch is that Symfony has progressively removed the Twig and templating extension points these tags lean on, so a future framework bump may make the bundle uninstallable rather than merely unsupported. Verify the tags still work on your exact Symfony version before planning an upgrade around them.
- Is Assetic safe to run in production?
- Assetic itself is end-of-life, and there is no vendor patch route for a CVE in Assetic or in a pinned filter binary such as lessc or uglify-js. Transitive packages including kriswallsmith/assetic, Twig and Symfony components will drift out of security support. It is only defensible as a short-lived shim inside a legacy application that already uses Assetic, with a committed migration timeline.
- What should I use instead of Assetic in a modern Symfony application?
- Use Symfony Encore (Webpack), AssetMapper, or Vite. For any greenfield or modern Symfony project one of those is the correct answer and this bundle is not a candidate at all. If you are migrating, inventory which Assetic filters the app actually uses and confirm each one has a one-for-one replacement in the target toolchain before committing.
- How do I handle the assetic:dump step in a deploy pipeline?
- The bundle presupposes a server-side build and dump step, so assetic:dump must be wired into your deployment or, preferably, into the image build. That requirement conflicts with immutable container and CDN-fronted delivery patterns, so run the dump at build time and ship the compiled assets rather than compiling on running hosts. Also watch cache-warmup ordering, since cache warmup can run before assets exist.
- How do I migrate a legacy Symfony app off Assetic?
- Start by listing every filter and Twig tag in use, then map each one to Encore, AssetMapper or Vite and convert the templates before removing the bundle and its configuration. Run the old and new pipelines in parallel for a release so you can compare output. Keep the fork in place only as a temporary unblock for a PHP or Symfony upgrade, with a named owner and a dated removal plan.