- Is ju1ius/webpack-assets-bundle a Laravel package?
- No. It is a Symfony2 bundle under the ju1ius\WebpackAssetsBundle namespace, built around Symfony primitives such as a Bundle subclass, a DependencyInjection extension, and Twig helpers. Laravel's service provider and Blade model is a conceptual cousin but not a compatible target. Treat it as a Symfony package, not a Laravel dependency.
- Can I use ju1ius/webpack-assets-bundle in a Laravel application?
- You can technically install it with Composer, but nothing will auto-register and the Symfony container wiring will not resolve in Laravel. The bundle's bootstrapping, configuration binding, and templating hooks all require rewriting. Consuming it directly in a Laravel app is possible but pointless compared with porting the small manifest-resolution logic.
- What does ju1ius/webpack-assets-bundle actually do?
- It reads Webpack manifest data to resolve logical asset names to hashed, production-ready URLs. Templates can then reference stable names instead of build-specific filenames. It supports Webpack entrypoints and chunks, and exposes Twig integration for emitting asset URLs, with configurable manifest paths and web roots.
- Which Laravel versions does this package support?
- None officially. There is no Laravel support declared or implied, and the package's integration surface targets Symfony2 rather than Laravel's service provider and facade system. Any Laravel use would require a shim or a rewrite of the integration layer. Do not expect Laravel version compatibility to be maintained.
- How do I install and configure ju1ius/webpack-assets-bundle in a Symfony app?
- It is installed via Composer and registered as a Symfony2 bundle in AppKernel. Configuration goes through the bundle's configuration tree, which covers manifest locations and public paths so the resolver knows where to find build output and how to expose it. Because the README excerpt is incomplete, verify exact config keys against the repository before relying on them.
- Can I use its Twig helpers in Laravel Blade templates?
- No, not directly. The package exposes Twig integration, and Blade does not run Twig extensions. To get similar behavior in Laravel you would need to re-implement the helper as a Blade directive or a PHP helper, backed by your own manifest resolver. That port is small, but it is not provided by this package.
- Does ju1ius/webpack-assets-bundle support Webpack 5 and modern manifest formats?
- There is no evidence that it does. The last release was in January 2016, which predates Webpack 4 and 5, so its stats-file parsing assumptions are likely stale. Whether it works with webpack-manifest-plugin output or a custom emitter depends on the exact manifest format, and you should verify that before considering any port.
- Is ju1ius/webpack-assets-bundle still maintained?
- No. The last release was 2016-01-11, the repository has around 14 stars and zero dependents, and there is no evidence of maintenance for roughly a decade. The MIT license removes legal friction but not maintenance risk. Adopting it means owning an orphaned codebase with no downstream pressure to keep it working.
- What are the Laravel alternatives for resolving Webpack manifest assets?
- Laravel already solves this through Vite, which reads the build manifest and provides the @vite Blade directive and helper ergonomics. Older applications commonly use Laravel Mix. If you have a genuine capability gap such as a shared multi-app manifest or CDN prefixing, confirm that first, because the native Vite or Mix route usually covers it without adding a Symfony dependency.
- How hard is it to port the manifest resolution logic to Laravel?
- Reasonably easy if you scope it narrowly. Build a WebpackManifest service that loads the manifest once per request, caches it, and resolves logical names to hashed paths; bind it as a singleton in a service provider with publishable config for manifest path, public prefix, and dev-versus-prod behavior. Add a Blade directive and an asset_manifest helper, and throw on missing keys in production instead of silently falling back. That is days of work, fully owned, and inherits Laravel's testing and upgrade conventions.