- What is jbaron-mx/laravel-recombee and what does it do?
- jbaron-mx/laravel-recombee is a Laravel wrapper around Recombee's recommendation API. It provides a fluent, Eloquent-style interface for personalized recommendations, search, and user-item interaction tracking inside a Laravel application. It is Laravel-native, so it is intended to register through a service provider rather than require custom wiring.
- How do I install jbaron-mx/laravel-recombee in a Laravel app?
- Install it with Composer using composer require jbaron-mx/laravel-recombee. Laravel package auto-discovery should register the service provider if the package follows standard conventions, but confirm that in the source or README. You will also need Recombee API credentials and any publishable configuration; check the repository README for the exact config and publish commands before wiring it into an app.
- Which Laravel versions does laravel-recombee support?
- The 0.2.2 release is reported to add Laravel 13 support, and the package tracks Laravel's release train. Before adopting it, open composer.json and verify whether the Laravel constraint was widened to include 11 and 12 or replaced with only 13. That distinction matters if you are not yet on Laravel 13.
- Is laravel-recombee safe for production use?
- Treat it as usable but not battle-proven: it is at 0.x, which means no backward-compatibility guarantee even across patch or minor releases. Install it in a throwaway Laravel 13 app first, confirm it boots without deprecation notices, then pilot it in one non-critical service. Pin the exact version and keep a record of the package version against your Laravel version.
- How is laravel-recombee different from using the Recombee PHP SDK directly?
- The direct Recombee PHP SDK gives you the raw client and requires you to handle Laravel wiring yourself. This package wraps that SDK in a fluent, Eloquent-style API and is Laravel-native, so it should reduce boilerplate for service-provider registration and configuration. The tradeoff is an extra framework-coupled dependency at 0.x, so read the source before putting it in a critical path.
- Does laravel-recombee support personalized recommendations and search?
- Yes. The package overview explicitly lists personalized recommendations, search, and user-item interaction tracking as the capabilities it exposes through its Laravel wrapper. The underlying work is done by Recombee's API; the package's value is the fluent Laravel-style interface around it.
- How do I track user-item interactions with laravel-recombee?
- The package advertises user-item interaction tracking as part of its Recombee wrapper, which is how you feed behavioral signals into recommendations. The exact method names and payload shape are not in the overview, so check the README and source for the interaction-tracking API. Verify that tracking calls are safe to run in the request path or move them to a queue if latency matters.
- Is jbaron-mx/laravel-recombee actively maintained?
- The 0.2.2 release is a positive signal because it keeps the Laravel compatibility matrix current. It is only one data point, though: check commit cadence, open issues, PR responsiveness, and download volume before relying on it. Assume community support at 0.x and make sure someone on your team can read and patch the source if needed.
- Should I pin laravel-recombee to an exact version?
- Yes. Pin 0.2.2 exactly rather than floating ^0.2, because at 0.x a minor version bump is allowed to introduce breaking changes without the version number warning you. Record the pinned version alongside your Laravel version and tested date, and re-check it during framework upgrades.
- What are the alternatives to jbaron-mx/laravel-recombee?
- The main alternative is using the Recombee PHP SDK directly and writing your own Laravel service provider or wrapper. You could also evaluate other Laravel recommendation packages, but compare their maintenance cadence, Laravel version constraints, and 1.0 status. For a non-critical pilot, this package's fluent API may be worth the 0.x risk; for a critical path, prefer the option with the clearest support and test coverage.