- Can I use presta/composer-public-bundle in a Laravel application?
- No. It is a Symfony 2 bundle that depends on Symfony's Kernel and bundle registration, and there is no service provider, facade, or config publish hook for Laravel. Laravel's package discovery and asset pipeline share no integration surface with it. Use npm plus Vite for front-end dependencies instead.
- Does presta/composer-public-bundle support Laravel 10 or Laravel 11?
- No. The package was last released in 2014 for Symfony 2 and has no Laravel version support at all. It predates modern PHP and Composer 2, so it will not install or run in a current Laravel project. There is no supported path to register it inside Laravel.
- How do I install presta/composer-public-bundle?
- Installation only makes sense in a legacy Symfony 2 project using Composer 1.x and a contemporaneous Composer installer plugin. You add the bundle to your Symfony kernel and declare third-party assets in the composer.json extra block. Modern Composer 2 resolves or rejects that schema differently, so installation is not supported today.
- Is presta/composer-public-bundle maintained?
- No. The last release was 2014-02-25 and the repository is archived. It has 3 stars and 0 dependents, so there is no community to report or patch security issues. Treat it as abandoned and do not adopt it for new work.
- What should I use instead of presta/composer-public-bundle in Laravel?
- Use npm, pnpm, or yarn to declare front-end dependencies and build them with Vite, which is the Laravel default since Laravel 9 and 10. This gives you lockfiles, integrity hashes, and security advisories that the bundle never provided. For legacy Symfony, use Symfony AssetMapper or Webpack Encore.
- Can presta/composer-public-bundle manage JavaScript and CSS assets in Laravel?
- No. The bundle's purpose is to declare third-party JS, CSS, and images in composer.json and have them fetched into a Symfony web root. Laravel's asset pipeline uses public/, Mix, or Vite, and there is no mapping for the bundle's conventions. A modern front-end toolchain already does this better.
- Is presta/composer-public-bundle safe for production?
- No. It is archived, unpinned, and low-visibility, which creates elevated supply-chain exposure for executable front-end assets. It predates PHP 7 and will emit deprecations or hard failures on PHP 8.x. Risk cannot be reduced by configuration; the only safe option is not to use it.
- What PHP versions does presta/composer-public-bundle support?
- It was built for the Symfony 2 era before PHP 7, so it does not support PHP 8.x. You can expect failures from removed functions like each() and create_function(), as well as dynamic property deprecations. Its dependency constraints will also conflict with modern symfony/* and composer/* requirements.
- How does presta/composer-public-bundle compare to Laravel Mix or Vite?
- It is not comparable. The bundle is a Symfony 2 Composer asset installer, while Mix and Vite are modern front-end build tools with lockfiles, integrity hashes, and active security support. Vite is the current Laravel default and fully replaces the bundle's capability.
- Can I test presta/composer-public-bundle with Laravel's test suite?
- No. There is no Laravel service provider or test integration, so Laravel's testing helpers cannot exercise it. In its native Symfony 2 habitat it requires an old Composer installer plugin and a PHP version that modern test runners do not support. Testing it inside Laravel is not a meaningful scenario.