- Is enius/whereby-bundle compatible with Laravel?
- No, enius/whereby-bundle is a Symfony bundle, not a Laravel package. Laravel does not consume Symfony bundles through package discovery, bundle registration, or config-tree integration. Using it in Laravel requires manually binding services in a ServiceProvider or bypassing the bundle layer and calling the underlying Whereby client classes directly.
- How do I install enius/whereby-bundle in a Laravel app?
- You can try composer require enius/whereby-bundle, but expect dependency resolution to fail or force downgrades on Laravel 10 or 11. Install it on a throwaway branch first and run composer why-not to expose Symfony component conflicts. If you proceed, register any usable services manually in a Laravel ServiceProvider.
- What Whereby API features does enius/whereby-bundle support?
- The bundle is a thin Symfony wrapper over Whereby's REST API for creating and retrieving meeting rooms and embedding calls. The last release was 2020-10-26, so it likely targets an older Whereby API contract and auth model. Confirm endpoints and authentication against current Whereby documentation before relying on it.
- Does enius/whereby-bundle support Laravel 10 or Laravel 11?
- There is no declared Laravel support, and the package is a Symfony bundle from 2020. Its PHP and Symfony constraints are likely to conflict with the Symfony 6 or 7 components pinned by Laravel 10 and 11. Treat it as incompatible unless a timeboxed dependency spike proves otherwise.
- What PHP and Symfony versions does enius/whereby-bundle require?
- The package context does not provide reliable current constraints, and its 2020 release suggests older Symfony and PHP requirements. Read composer.json and run composer why-not against your application to see exact conflicts. Validate PHP, Symfony component, and Guzzle major versions before considering any adoption.
- Can I use enius/whereby-bundle without Symfony?
- Only if its core classes do not hard-depend on Symfony's DI container, HttpClient, or Config components. Inspect the source first, because cherry-picking classes may still drag Symfony components into Laravel and conflict with pinned versions. If dependencies are isolated, reuse the small wrapper logic rather than the bundle layer.
- Is enius/whereby-bundle maintained and secure?
- The package has zero stars, zero dependents, no upstream community, and a last release date of 2020. There is no security response path, CVE monitoring, or maintainer SLA. Adopting it means owning the code and every Whereby API change as an internal incident.
- What is a better Laravel alternative for Whereby video meetings?
- Build a first-party WherebyClient using Laravel's Http facade, credentials in config/services.php, typed DTOs for meeting payloads, and a service provider for binding. This preserves Laravel idioms such as facades, config caching, and HTTP fakes in tests. Also check whether Whereby offers an officially supported SDK before writing custom code.
- How do I test Whereby room creation in Laravel?
- With a native Laravel HTTP client, use Http::fake() and assert the request payloads sent for meeting or room creation. A Symfony bundle layer is not designed for Laravel's HTTP fakes, so wrap any reused bundle entry point behind a MeetingProvider interface. Contract tests should also verify current Whereby authentication and endpoints.
- Should I use enius/whereby-bundle in production?
- It is not recommended for a Laravel production application because of the Symfony architecture mismatch, deprecated API risk, and lack of maintenance or security response. Treat it as a reference implementation rather than a dependency. If reuse is mandated, feature-flag the provisioning flow and shadow-run it with sandbox credentials before committing.