- Does gnugat/search-engine-bundle work with Laravel?
- It is a Symfony bundle, not a Laravel package, and there is no evidence of a Laravel service provider, facade, config file, or publishable assets. You could only use it in Laravel if Composer resolves its dependencies and you manually wire the library services into Laravel's container. Modern Laravel applications are likely to conflict with its Symfony 3 and PHPUnit 5-era constraints.
- How do I install gnugat/search-engine-bundle with Composer?
- Install it with composer require gnugat/search-engine-bundle, but pin an exact version because the package is pre-1.0 and has limited API stability guarantees. Run composer why-not against your target Laravel and PHP versions before merging anything. Do the install in a disposable branch so you can roll back cleanly if resolution fails.
- Which Laravel and PHP versions are supported?
- No Laravel support matrix is published for this package. The only release evidence, v0.3.1, mentions Symfony 3 and PHPUnit 5 support, which aligns with older Laravel 5.x-era stacks rather than Laravel 9 through 12. Treat modern Laravel and PHP 8+ compatibility as unproven until you verify the Composer constraints yourself.
- Do I need a Laravel service provider to use it?
- The bundle integrates with Symfony's dependency injection container, and no Laravel service provider or facade is documented. In a Laravel app you would need to bind the search engine, index, and mapping services manually or wrap them behind your own adapter. Isolating it behind an internal interface limits upgrade friction if you later replace it.
- Can I use Doctrine or array data sources with it in Laravel?
- The underlying library is data-source agnostic and supports pluggable sources through tagged services. Symfony's tag-based autoconfiguration does not translate directly to Laravel, so you would register your Doctrine repository or array source manually in the container. The abstraction still works, but you lose the automatic wiring the bundle provides in Symfony.
- Is gnugat/search-engine-bundle safe to use in production?
- There is no published security policy, maintenance cadence, or test coverage evidence, and the package is pre-1.0. Its Symfony 3 and PHPUnit 5-era dependencies are legacy and may block PHP 8+, modern CI images, and current static analysis tooling. Pin the exact version, run a security and license review, and avoid introducing it into a modern Laravel app without a compatibility spike.
- How do I test a Laravel application that uses this bundle?
- PHPUnit 5 appears to be a development-era dependency, so the package's own tests will not run under current PHPUnit versions. You can still write your own tests against an adapter layer using your application's normal test setup. Run the full unit, integration, and regression suite in a disposable branch before adopting it.
- What are the alternatives to gnugat/search-engine-bundle for Laravel search?
- Laravel Scout with TNTSearch, Meilisearch, or Algolia drivers is the native path, and Elasticsearch clients are common for larger datasets. This bundle is framework-agnostic engine plumbing for indexes, mappings, and queries rather than a Laravel search driver. Choose Scout unless you specifically need the index and mapping abstraction.
- Is gnugat/search-engine-bundle actively maintained or abandoned?
- The available evidence is limited to v0.3.1 release notes adding Symfony 3 and PHPUnit 5 support. No changelog, support matrix, or maintenance cadence is provided, so treat it as unproven and pre-1.0. Check Packagist release history and repository activity before committing to it.
- Will it conflict with my existing Laravel Composer dependencies?
- It may, especially if it constrains Symfony 3 components or PHPUnit 5, since current Laravel releases require newer Symfony components and PHPUnit versions. Run composer why-not against your Laravel, PHP, and PHPUnit versions and perform a resolution spike in a disposable branch. If resolution fails, isolate the package or pick a maintained alternative instead of forcing constraints.