Weave Code
Asset Bundle Laravel Package
integrated/asset-bundle
Integrated Asset Bundle is a Laravel package for managing and serving front-end assets, bundling CSS and JavaScript into optimized files and simplifying asset registration, versioning, and publishing within PHP applications.
At a glance
Frequently asked questions about Asset Bundle
- How do I install integrated/asset-bundle in a Laravel app?
- Install it with composer require integrated/asset-bundle, then confirm the service provider is registered or relies on Laravel package discovery. Because the -bundle suffix and Symfony Asset component suggest Symfony lineage, check composer.json for laravel/framework and php constraints before installing into a Laravel application. Publish any config stub with php artisan vendor:publish and define your asset collections.
- How do I configure asset collections in YAML or PHP?
- Collections are declared in YAML or PHP config, with each collection mapping a name to source paths, output paths, and filters such as minification or combining. After configuring, run the publish or filter command to generate versioned output and reference collections from templates. The exact keys depend on the package version, so read the shipped config stub rather than guessing.
- Which Laravel and PHP versions does integrated/asset-bundle support?
- The README excerpt provided does not state supported Laravel or PHP versions. Check the require and require-dev blocks in composer.json, since those constraints are what Composer actually enforces. With zero dependents and no issue history, do not assume current Laravel support without a short verification spike.
- How is Integrated Asset Bundle different from Laravel Vite?
- Laravel's default is Vite: a build produces manifest.json and Blade calls Vite::asset(). This package advertises its own collection config and template helpers, which creates a second resolution path for asset URLs and hashed filenames. Adopt it only when you can name a gap Vite does not close, such as legacy manifest-style resolution or publishing versioned assets from a package.
- Can Integrated Asset Bundle consume a Vite manifest.json?
- That is unconfirmed in the material provided. The package is built on Symfony's Asset component and advertises its own publish and filter pipeline, which suggests it may expect its own compiled output instead of a Vite manifest. If it cannot read manifest.json, you add a second build step with real CI-minute and onboarding cost.
- How do I use the asset helpers in Blade templates?
- The overview documents Twig helpers and bundle-relative path resolution, which is Symfony terminology. The technical assessment lists Blade directives as a claim to verify, and the README excerpt does not demonstrate them. Confirm the actual directive or helper names in the service provider before writing Blade templates against them.
- Does the package write compiled assets to public/ at runtime?
- The publish and filter pipeline writes generated assets somewhere, most likely under public/. Whether that happens at build time or during a runtime request is the critical question for deployments. Runtime writes to public/ break read-only or hardened containers, so require a build-time-only command for production.
- Are the versioned asset URLs deterministic across builds?
- Versioned URLs for cache busting are advertised, but that claim alone does not guarantee content-stable hashes. Run two consecutive builds and diff filenames and file contents; identical output is the acceptance test. Non-deterministic hashes will churn caches and undermine long-lived CDN caching.
- Is integrated/asset-bundle safe to use in production?
- Treat production use as high risk until proven otherwise: zero stars, zero dependents, no issue history, and a single-maintainer signature mean no community absorbs the project if upstream stops. Pin to a commit SHA rather than a floating constraint. Budget a bounded spike with written acceptance criteria before adopting.
- What are the alternatives to Integrated Asset Bundle for Laravel?
- For most Laravel applications the alternative is Vite with Vite::asset() and manifest.json, optionally with CDN or cache-header configuration. Legacy stacks may still use Laravel Mix, and teams needing Symfony-style asset handling can use the Symfony Asset component directly. A small custom manifest helper is often cheaper than adding a second asset abstraction.
Weaver
How can I help you explore Laravel packages today?