Weave Code
Laravel Bento Laravel Package
exolnet/laravel-bento
Exolnet's Laravel Bento is a lightweight package for building modular dashboards from reusable widgets and cards. Compose responsive admin layouts, configure panels, and add metrics or custom views with a simple API, ideal for internal tools and admin panels.
Organize feature launches by custom user segments.
Frequently asked questions about Laravel Bento
- What is exolnet/laravel-bento used for?
- It is a thin Laravel integration layer over the Bento tracking and email API, providing a service provider, a manager and facade binding, a publishable config file, and event and queue hooks. You use it to send tracked events from a Laravel application so Bento can organize feature launches by custom user segments. The package deliberately avoids imposing architectural opinions beyond the container and queue.
- Which Laravel and PHP versions does laravel-bento 2.9.0 support?
- Version 2.9.0 explicitly drops Laravel 11 and adjusts PHP support to 8.4, which in context reads as a minimum rather than a maximum tested version. Effective support is therefore Laravel 12 or newer on PHP 8.4 or newer. The release note does not state the resulting lower bounds, so confirm both the laravel/framework and php constraints in composer.json before relying on them.
- How do I install laravel-bento?
- Require it with Composer, publish its config file, and supply your Bento credentials through environment variables. Because the package is a thin service provider plus configuration, installation is low-friction on a compatible stack. Confirm your app is already on Laravel 12 and PHP 8.4, otherwise Composer will fail to resolve the ^2.9 constraint.
- Why can't Composer install laravel-bento ^2.9 on my Laravel 11 app?
- Version 2.9.0 drops Laravel 11 and raises the PHP floor to 8.4, so the constraint is genuinely unsatisfiable on that stack rather than a cache or mirror problem. Run composer why-not exolnet/laravel-bento ^2.9 to surface the exact blocking constraints. In the interim, pin explicitly to 2.8.* so Composer cannot resolve into a release your application cannot run.
- Is upgrading from laravel-bento 2.8 to 2.9 a breaking change?
- Effectively yes, even though it shipped as a minor version bump from 2.8.0 to 2.9.0. Dropping a framework major and raising the PHP minimum breaks any app on Laravel 11 or PHP below 8.4, and a ^2.8 constraint will silently resolve to it. The changelog is a single line and states no API change, but that is not proof there is none, so read the diff for PR #58 before adopting.
- How do I configure laravel-bento API credentials?
- Publish the package config file and provide your Bento credentials, typically via environment variables rather than committing secrets. When upgrading, merge the newly published config instead of overwriting your existing file, and check whether any keys were renamed in 2.9.0. Since the config is publishable, it is safe to version the merged result per environment.
- Does laravel-bento send tracked events through the queue?
- Yes, the package exposes event and queue hooks, so tracked events can be dispatched asynchronously from a standard Laravel queue. After upgrading, exercise the queue path end to end by dispatching a tracked event in a dev environment and confirming delivery. Worker and queue configuration stays in your application, so normal Laravel queue monitoring applies.
- What is the safest upgrade path to laravel-bento 2.9?
- Do it in sequence: upgrade PHP to 8.4 and clear deprecations across your whole dependency tree, then move the framework to Laravel 12 while resolving packages that pin below it, and only then bump laravel-bento to ^2.9. Trying the package bump first is the most likely failure mode because it produces an unsatisfiable constraint. Audit your lockfile for anything holding laravel/framework at 11 or php below 8.4 before starting.
- Will laravel-bento 2.8.x keep receiving bug and security fixes?
- That is not stated anywhere in the release, and raising the floor this aggressively on a low-traffic community package suggests the maintainer may intend to track only the current Laravel release. Ask the maintainer directly whether a 2.8.x branch will be patched and for how long. Until you have an answer, pin explicitly to 2.8.* and treat future minor releases as potentially unsafe to auto-adopt.
- How do I test laravel-bento without calling the real Bento API?
- Because the package is a thin binding over the Bento API, you can keep tests hermetic using Laravel HTTP client fakes and Queue::fake, asserting that events were dispatched without real network calls. Swap or mock the manager binding if you need to assert at the package boundary. Run the queue path once in a dev environment before production to confirm delivery works after the upgrade.
Weaver
How can I help you explore Laravel packages today?