Weave Code
Framework Laravel Package
assetic/framework
Assetic is a PHP asset management framework for combining, minifying, and compiling CSS, JavaScript, and other front-end assets through configurable filters and pipelines. It integrates with frameworks such as Symfony to streamline asset processing and delivery.
Asset Management for PHP
Frequently asked questions about Framework
- How do I install and use assetic/framework in a Laravel application?
- Install it with Composer, then hand-wire your own service provider that constructs the AssetFactory, FilterManager, and AssetWriter. There is no first-party Laravel bridge in this repository, so you must define asset collections and filter chains in PHP instead of Symfony YAML. You will also need an Artisan or Composer command to dump compiled assets at build time.
- Does assetic/framework support Laravel 11 or other recent Laravel versions?
- Assetic is framework-agnostic PHP at its core, so it has no Laravel version constraint and can run inside current Laravel releases if you wire it yourself. The catch is that no official Laravel integration ships with the package, so compatibility and upkeep are your responsibility. The closest existing consumer is October CMS, which vendors its own integration layer you cannot directly reuse.
- How do I reference Assetic-compiled assets in Blade templates?
- Assetic writes compiled files to a web-served directory, but it does not provide Blade helpers or manifest resolution for Laravel. You need to build a manifest or helper that maps logical asset names to hashed output paths and expose it through a Blade directive. Without that layer, you get none of the automatic URL and cache-busting behavior Laravel developers expect from Vite.
- What external binaries does Assetic need for its filters?
- Most Assetic filters shell out through symfony/process to external tools such as lessc, sass, java for YUI Compressor, node or uglifyjs, and optipng or jpegtran. Your container image or build agent must therefore carry a Java runtime and Node toolchain in addition to PHP. That coupling is exactly what modern Laravel pipelines based on Vite and esbuild are designed to avoid.
- Is assetic/framework a good alternative to Laravel Vite?
- For greenfield Laravel applications, usually not. Assetic compiles assets on the fly in development and dumps them to disk in production, which is orthogonal to Vite's dev server with HMR and manifest-driven production builds. Running both creates two source-of-truth pipelines for asset URLs and cache busting.
- How do I dump or compile Assetic assets during a Laravel deployment?
- Create an Artisan command or Composer script that calls the AssetWriter's write method, and run it as a deploy step rather than at request time. Cache invalidation should be tied to deploys so compiled filenames and manifests stay consistent. This mirrors Assetic's dump-to-disk production model rather than on-the-fly compilation.
- Is assetic/framework actively maintained and safe to use in production?
- The fork shows active patch releases, and the recent v3.2.3 patch was authored by LukeTowers, a known figure in the October and Winter CMS ecosystem. However, the repository shows roughly 101 stars and zero dependents, which strongly suggests a fork or re-upload rather than the original package's historic install base. Treat continuity as plausible but downstream validation as absent, and review the security surface yourself before production use.
- What security issue does assetic/framework v3.2.3 fix?
- v3.2.3 applies import validation consistently across the CSS and SCSS filters, hardening the point where template-influenced import paths reach the filesystem. The changelog does not claim equivalent validation for the LESS, JavaScript, CoffeeScript, or image filters. The broader risk of interpolating paths into symfony/process shell-outs remains architectural and is not eliminated by this patch.
- Can I use Assetic filters such as LESS, Sass, and CoffeeScript inside Laravel?
- Yes, but you must manually register each filter with the FilterManager and supply the correct binary paths. Filter chains are configured in PHP rather than Symfony YAML, and any filter that shells out needs its external compiler installed on the build machine. There is no Laravel bundle to provide these definitions for you.
- How does Assetic's asset collection model compare with Laravel Mix or Vite?
- Assetic uses an AssetFactory to build named asset collections and dependencies, a FilterManager to resolve named filters, and an AssetWriter to dump compiled output. That model is powerful and framework-agnostic, but its ergonomics were designed around Symfony's DI container and bundle conventions. In Laravel you would be reimplementing what AsseticBundle used to provide for free, whereas Mix and Vite ship Laravel-native configuration and helpers.
Weaver
How can I help you explore Laravel packages today?