- Can I install rmzamora/jquery-bundle in a Laravel application?
- Composer installation may succeed only if its legacy Symfony dependencies resolve, but the package is not designed for Laravel. It does not provide a Laravel service provider, facade, config publishing, or Vite integration. The technical evaluation recommends not integrating it into a Laravel app. If jQuery is required, install it through npm and bundle it with Vite instead.
- Is rmzamora/jquery-bundle a Laravel package?
- No. It is a Symfony bundle that expects Symfony bundle registration, the DI container, and likely a Twig or Assetic asset pipeline. Laravel uses service providers and Vite or Mix for front-end assets, so there is no architectural alignment. jQuery itself should be managed as a front-end dependency, not as a PHP package.
- How do I add jQuery to a Laravel app without this bundle?
- Run npm install jquery, import it in your JavaScript entry point, and let Vite bundle it for Laravel. For a quick legacy path, you can include a pinned jQuery CDN asset with Subresource Integrity. This avoids a Symfony-to-Laravel bridge and keeps jQuery under your normal front-end dependency management.
- Does rmzamora/jquery-bundle support Laravel 10 or Laravel 11?
- There is no declared Laravel support. The package is a Symfony bundle, and its Composer constraints may conflict with modern Laravel or Symfony components. The evaluation notes likely incompatibility with modern Laravel and PHP. Do not rely on it for Laravel 10 or 11; use a Laravel-native asset approach.
- Which Symfony and PHP versions does rmzamora/jquery-bundle support?
- The available context does not list exact Symfony or PHP constraints, and the README excerpt is empty. The repository is archived and likely pins old Symfony versions, so you must inspect composer.json before attempting any install. Expect dependency resolution problems with current Laravel and PHP versions.
- Is rmzamora/jquery-bundle maintained and safe for production?
- No. The repository is archived, has zero stars and zero dependents, and has no community validation or upstream support. Archived status means no security patches, no PHP or Laravel compatibility updates, and high supply-chain risk. For production Laravel apps, the evaluation recommends avoiding it entirely.
- Which jQuery version does rmzamora/jquery-bundle ship, and does it have known CVEs?
- The context does not specify the bundled jQuery version. The evaluation warns it may ship an outdated jQuery release with known vulnerabilities. Inspect the package assets and lockfile, then run software composition analysis before any use. A better path is to pin a current jQuery version through npm or a CDN with SRI.
- Can I vendor only the jQuery JavaScript asset without adopting the Symfony bundle?
- Conceptually yes: you could extract a static JS asset and include it in Laravel's public assets or Vite pipeline. However, you must verify the license, the exact jQuery version, and any known CVEs first. The evaluation treats the bundle as a reference only and recommends replacing the PHP integration with a Laravel-native asset pipeline.
- How should I test or spike rmzamora/jquery-bundle in Laravel?
- Do it in an isolated branch and run composer require expecting dependency or autoload failures. Document the results and do not merge the spike into a production branch. Test the Laravel-native alternative in parallel by installing jQuery via npm and verifying Vite asset loading. The expected outcome is to record a decision against using the bundle.
- What are Laravel-native alternatives to rmzamora/jquery-bundle?
- Use npm to install jquery and bundle it with Vite, which is the standard Laravel front-end workflow. Laravel Mix remains an option for older applications, and a pinned CDN asset with SRI can work for legacy pages. There is no need for a Symfony bundle or PHP-mediated asset pipeline in Laravel.