- Does maba/webpack-bundle work with Laravel?
- No. It is a Symfony bundle that depends on Symfony's bundle system and FrameworkBundle, and it has no Laravel service provider or facade integration. Installing it in a Laravel app would add a Composer dependency that does nothing at runtime. For Laravel, use Vite or Mix, or write a small manifest reader if you only need hashed asset resolution.
- How do I install maba/webpack-bundle in a Symfony app?
- Install it with Composer and enable the bundle in your Symfony 4 or 5 kernel or bundles.php, then configure the build and public paths for your Encore output. Check the PHP and Symfony constraints before installing because the last release is from January 2020. Follow the package README for the exact configuration keys instead of assuming current Symfony conventions.
- What do encore_entry_script_tags() and encore_entry_link_tags() do?
- These Twig helpers render script and link tags for a named Webpack entry, using entrypoints.json to include dependencies in the correct order. They let templates reference logical entry names instead of hard-coded hashed filenames. The bundle also exposes a WebpackEncore service so controllers and other services can render the same tags.
- How does maba/webpack-bundle resolve hashed asset filenames?
- It reads the Encore-generated entrypoints.json and manifest.json files and maps logical entry names to the versioned filenames on disk. That keeps cache-busted assets working consistently across environments. You configure the build and public paths so the bundle knows where to find those JSON files.
- Is maba/webpack-bundle still maintained?
- It appears effectively unmaintained: the last release was 2020-01-17, it has a single maintainer and very few dependents. It predates Symfony 6, Symfony 7, and modern PHP 8.x validation. The MIT license makes forking or vendoring legally clean if you must keep it alive, but that is a maintenance commitment.
- What is the difference between maba/webpack-bundle and symfony/webpack-encore-bundle?
- symfony/webpack-encore-bundle is the first-party successor and covers the same Encore entrypoint and manifest resolution concern with active maintenance. maba/webpack-bundle is a third-party bundle with no upstream incentive to patch it. For new Symfony work, choose the official Encore bundle or an in-house manifest resolver.
- Can I use maba/webpack-bundle with Symfony 6, Symfony 7, or PHP 8?
- Treat that as unsupported unless you verify it with a CI spike. The January 2020 release predates Symfony 6 and PHP 8 hardening, so expect deprecation noise or hard failures from removed container APIs. Pin the version and test bundle boot, container compilation, and Twig rendering before committing to it.
- What does strict mode do in maba/webpack-bundle?
- Strict mode makes missing Webpack entries fail loudly instead of silently rendering incomplete or empty asset tags. That is useful in production because a typo in an entry name should not ship a broken page. Validate the exact behavior in your installed version, since older bundles often differ in exception type and message.
- How should I test asset resolution with maba/webpack-bundle?
- Use fixture entrypoints.json and manifest.json files that mirror real Encore output, then assert that the service returns the expected paths and that the Twig helpers render the right tags. Add a functional test that renders a template containing encore_entry_script_tags() and encore_entry_link_tags(). Keep the test matrix on PHP and Symfony versions the bundle actually supports.
- What is a Laravel alternative to maba/webpack-bundle?
- Laravel's native path is Vite through laravel-vite-plugin, or Laravel Mix on older applications; both handle asset URLs and cache busting. If you only need manifest resolution, a small in-house reader is cheaper than porting a Symfony bundle. Do not try to carry the Bundle class, DI extension, or config tree into Laravel.