- Can I use puntmig/search-bundle in a Laravel application?
- No, not directly as intended. It is a Symfony bundle built for the Symfony bundle and dependency injection lifecycle, and Laravel does not run that lifecycle. You can use Apisearch from Laravel through its PHP client or HTTP API, but this bundle should be treated as reference material rather than a runtime dependency.
- Does puntmig/search-bundle support Laravel package auto-discovery?
- No. The package is a Symfony bundle and does not provide Laravel auto-discovery, config publishing, facades, or Laravel-native service bindings. Any Laravel integration would require manual wiring around the Apisearch client, not the bundle.
- How do I install puntmig/search-bundle with Composer?
- You can install it with Composer, but it is not a Laravel package and direct installation will not give you a working Laravel integration. Before committing, check its Composer constraints against your PHP and Symfony component versions, since it was last released in 2021. For Laravel, prefer installing a maintained Apisearch client or an HTTP SDK instead.
- Is puntmig/search-bundle maintained and compatible with current Laravel versions?
- The repository is archived and the last release was in 2021, so there is no active maintenance or security path. Compatibility with current PHP and Laravel versions is unvalidated and may conflict with Laravel's supported Symfony components. Assume it is not production-ready for modern Laravel without a thorough compatibility spike.
- What Laravel versions does puntmig/search-bundle support?
- The package does not target Laravel versions at all; it is a Symfony bundle for Apisearch. It therefore has no documented Laravel support matrix, auto-discovery, or Laravel-specific configuration. You must validate any use against your target PHP and Symfony component constraints, not a Laravel version list.
- What should I use instead of puntmig/search-bundle for search in Laravel?
- For most Laravel applications, use Laravel Scout with Meilisearch, Typesense, or Elasticsearch, or a maintained Apisearch client behind a Laravel service provider. These options provide Laravel-native integration, active maintenance, and clearer operational support. Keep the Symfony bundle out of the Laravel runtime unless Apisearch is already a mandated platform.
- How do I integrate Apisearch with Laravel without the Symfony bundle?
- Use the Apisearch PHP client or HTTP API directly inside Laravel service classes. Create a config file, bind a singleton client, put indexing in queued jobs, wrap queries in a search service, and add health checks. Define SearchIndexer and SearchRepository interfaces so you can swap adapters and add a fallback.
- Is puntmig/search-bundle safe to use in production?
- The technical risk is high: the package is archived, has low adoption, and has no active security or maintenance path. Production use would rely on stale dependencies and undocumented Symfony coupling. If Apisearch is business-critical, budget an internal owner for upgrades, security review, monitoring, and fallback planning.
- Can I publish config or use facades from puntmig/search-bundle in Laravel?
- No. Those are Laravel package conventions, and this is a Symfony bundle with its own dependency injection and configuration model. Laravel will not auto-register the bundle or expose facades and publishable config for it. Any configuration must be handled by your own Laravel adapter.
- How do I migrate from puntmig/search-bundle to a Laravel-native search adapter?
- Run an isolated spike with the raw Apisearch client against sample Laravel models, then copy any useful bundle logic under the MIT license with attribution rather than depending on the bundle. Introduce SearchIndexer and SearchRepository interfaces, implement an Apisearch adapter and a fallback, backfill indexes, dual-write, compare relevance, then cut over with rollback. Validate latency and relevance before committing to the switch.